Patterns
Eight jobs that are solved by a combination rather than by one component. Each carries an anatomy, a map of the components involved, do/don’t pairs with the reason, and accessibility notes.
Entering data3
Forms, settings and sign-in: where the user tells the product something.
- FormsWhat a form is made of, which components carry which part, and the four decisions that decide whether it can be filled in.
- SettingsEvery setting answers one question first — does it apply now or on save. Everything else about the screen follows from that answer.
- AuthenticationNothing here is a special component — it is an ordinary form. Everything that matters is in the decisions, and most of them are about what not to say.
Finding the way2
Getting to the right screen and to the right record.
Showing and answering3
Tables and lists, feedback on an action, layers over the page.
- Data displayTen ways to show the same rows. The choice is decided by what the reader does next — compares, scans, or looks up one thing.
- FeedbackSeven components answer one question — where does the message go. Choosing wrong is why interfaces feel unresponsive rather than look wrong.
- OverlaysEleven components put content above the page. The choice between them is a choice about focus — who has it, where it returns, and what Escape closes.
Nothing here matches. Try the search for the whole site — ⌘K.