Without one, every screen is a negotiation: this modal's padding, that button's blue, three font sizes where one was meant. A design system decides once — spacing tokens, type scale, the button's variants — and every screen after inherits the decisions instead of relitigating them.
The return shows up in speed and consistency: new pages assemble from parts, redesigns touch tokens not files, and the product feels authored. The trap is scale-appropriateness — a five-page site needs five decisions and a stylesheet, not a component library with documentation.
Related terms
WCAG
The Web Content Accessibility Guidelines — the standard that defines what makes web content usable by people with disabilities; AA contrast is 4.5:1 for body text.
Semantic HTML
Using elements that mean what they contain — nav, article, button — so screen readers, crawlers and browsers understand the page for free.
Core Web Vitals
Google's three field metrics for loading, responsiveness and visual stability, measured on real visits rather than in a lab.
The bench this belongs to
Full-stackIf you can describe it, we can build it. React and Next.js on the front, Python or Node behind, Postgres underneath, shipped to somewhere you can afford to run.
