A free, self-paced textbook in 7 chapters. Read a chapter, then drill it with the 208 companion flashcards using spaced repetition.
A design system is a shared set of principles, components, patterns, and rules that helps teams build consistent products faster. It exists because individual product teams repeate...
A good design system rests on a small set of guiding principles that every team can repeat and apply. The most practical principle is to make the right choice the easiest choice: w...
Design tokens are named values for color, spacing, typography, and other primitives that can be reused across tools and code. They are the atomic layer of a system: instead of writ...
Atomic design, proposed by Brad Frost, gives teams a shared vocabulary for thinking about UI composition. Atoms are the smallest UI building blocks: a button, input, icon, or singl...
Accessibility should be built into a design system from the start so that every team inherits better behavior instead of fixing the same issues repeatedly. The shorthand a11y refer...
Documentation is the surface through which consumers actually experience the system. Component documentation explains when to use a component, how it behaves, and what variants or...
System adoption is the degree to which product teams actually use the design system in day-to-day work, and it is the most honest measure of value. Adoption often fails when the sy...