design system
A shared set of design decisions, reusable components and rules that keeps every screen of a company's products looking and behaving the same way.
In more detail
A design system is more than a component library: it includes the visual foundations (colours, type, spacing), the components built on them, their documentation and the process for changing them. Teams depend on it like shared infrastructure, so it is versioned and governed.
Examples
This course builds one in layers, from design tokens up to packaged, tested components.In the browser: It usually includes design tokens, a component library and usage guidelines. Putting design-system styles in their own cascade layer lets applications override them predictably without specificity tricks.Headless React primitives let a design system apply its own styles while reusing tested behaviour and accessibility.Related terms
- design token — A named design decision, such as a colour, font size or spacing value, stored as data so every platform can use the same value.
- component library — A package of ready-made interface building blocks, such as buttons and dialogs, that many applications install and reuse.
- layered architecture — Organising a system into ranked layers where each layer may only use layers below it.
- design system governance — The rules and processes for how a design system changes: who can contribute, how releases are versioned and how old APIs are retired.
- cascade layer — A named group of CSS rules, declared with @layer, whose priority in the cascade is set by layer order instead of selector specificity.
- component — A reusable, self-contained piece of interface, such as a card or a modal, with its own markup, styles and behaviour.
- headless component — A component that provides behaviour, state and accessibility but no styling, leaving the look entirely to the consumer.
Taught in
- Design Systems Architecture: Foundations, Layers & Taxonomy — Design Systems & Component Engineering
- Design Tokens: W3C Specs, Global, Semantic & Component Tokens — Design Systems & Component Engineering
- System Governance: Changesets, Semantic Versioning & Deprecation — Design Systems & Component Engineering
- CSS Cascade Layers: Taming Specificity Wars with @layer — Frontend Architecture & Web Platform
- CSS Custom Properties: Scoping, Fallbacks And Theming — Frontend Architecture & Web Platform
- useImperativeHandle: Controlled Ref Forwarding Boundaries — React 19 & Modern Component Architecture
- Slot Patterns And Headless UI Architecture in React — React 19 & Modern Component Architecture
- Accessible Headless Primitives: ARIA, Focus, And Keyboard — React 19 & Modern Component Architecture