Named values that carry design decisions, so a change happens once rather than in every consuming file.
Design system · Foundations
Tokens, components, governance and adoption
Design Systems
Building the shared vocabulary, and keeping it alive after the launch announcement.
11 entries across 3 categories
Design systems11
Category
Level
11 entries
The props a component exposes determine whether it gets used correctly or forked, which is the main failure mode of design systems.
Design system · Components
Documentation is the product. An undocumented system is a component library nobody can adopt correctly.
Design system · Practice
Who decides what goes in, how changes are proposed, and how the system stays coherent as more people touch it.
Design system · Practice
A system nobody uses is a cost centre, and adoption is won by making the system the easiest path rather than by mandate.
Design system · Practice
How the system changes without breaking the products built on it.
Design system · Practice
How work gets from a product team into the shared system without either blocking the team or degrading the system.
Design system · Practice
Supporting several visual identities from one system, which is a token architecture problem before it is a design problem.
Design system · Foundations
A component is finished when its parts, its states and the reason each variant exists are all written down.
Design system · Components
Two libraries claiming to be the same system will diverge. Decide where truth lives, and make the other side derive from it.
Design system · Practice
Count what is actually in production before deciding what the system should contain.
Design system · Practice
Everything in Design Systems, by category
The full contents of this section, so you can see the shape of it rather than only what a filter returned.