A shared language for better experiences.
Typography
Give every word a clear role.
DESIGN SYSTEM / COMPONENTS
Explore 50 components with anatomy, guidance, working examples, and typed APIs.
50 components
A shared language for better experiences.
Give every word a clear role.
Span the right number of columns at each breakpoint.
Act with a clear, specific label.
A compact action with an accessible name.
Collect one precise piece of information.
Give longer answers room to breathe.
Choose independent options.
Choose one answer from a visible set.
Apply a setting immediately.
Choose one option from a list.
Find and choose several options.
Choose a date in context.
Adjust a value within a known range.
Choose a minimum and maximum together.
Choose the beginning and end of a period.
Files stay in this browser. This example does not upload them.
Select files with clear boundaries.
Add compact, scannable context.
Explain a state and the next useful step.
Your latest changes are ready for review.
Keep people informed without losing context.
Show completion without guessing.
Make brief waiting understandable.
Preview the shape of arriving content.
Your foundations are connected.
Today, 9:24 AMCheck color, type, and density.
In progressApprove the reviewed changes.
Make a sequence of events easy to follow.
| Status | |||
|---|---|---|---|
| Button | 2.0 | Ready | |
| Text field | 2.0 | In review | |
| Menu | 2.0 | Ready |
Compare structured information.
Build a shared language for every product your team creates.
Group related content and actions.
Continue with your workspace
Create a new design system
Separate content with restraint.
Represent a person or team consistently.
Orient people at the top of an experience.
Provide useful context at the end.
Make the workspace structure visible.
Show location within a hierarchy.
A shared vocabulary for your product.
Switch between related views.
Keep a small set of destinations close.
Explain progress through a workflow.
Page 1 of 12
Move through a bounded set of results.
Make destinations recognizable.
This section is the link’s destination.
Jump to a meaningful section.
Organize contextual actions.
Give one decision focused attention.
Keep supporting work beside the page.
Separate a modal layer from its context.
Offer a short, optional explanation.
Reveal supporting detail on demand.
Keep a small task near its trigger.
Add your first component to start a reusable library.
Explain what is missing and how to begin.
Give every field a clear name.
Put useful guidance beside the decision.
Space creates a clear boundary around related ideas.
Create a predictable content surface.
Arrange content with a consistent rhythm.
Let content find its natural columns.