Design Systems & Platform
Reference Design Systems
Maintained by IBM, Atlassian, Shopify, Salesforce, Microsoft
Mature, fully public enterprise design systems worth reading as reference architecture for tokens, governance, and documentation.
Why it matters
When you are building a system, the hardest problems are governance and documentation, not components. These are the best public examples of both solved at scale.
Key principles
- Every mature system documents contribution and deprecation processes, not just components.
- Token layering - primitive, semantic, component - is what makes multi-brand theming possible.
- Content and writing guidelines belong in the system; inconsistent microcopy is as visible as inconsistent spacing.
- Publish accessibility status per component so consumers know what they are inheriting.
Resources
Foundations, principles, tutorials, community Figma files, icon sets, and templates.
- ReferenceIBM Carbon - strongest token and accessibility docs
- ReferenceAtlassian Design System - content and writing guidance
- ReferenceShopify Polaris - exemplary UX writing patterns
- ReferenceSalesforce Lightning - enterprise scale and governance
- ReferenceMicrosoft Fluent 2
- FoundationDesign Systems Repo - curated index