| name | tokens |
| description | Design system governance - versioning, documentation, tokens |
Nathan Curtis - Design System Governance
Design systems die without governance. Documentation, versioning, and maintenance keep systems alive.
Core Philosophy
The System is a Product
A design system is not a side project. It needs:
- Dedicated owners
- Release schedule
- User feedback loops
- Deprecation paths
Documentation is Interface
If it's not documented, it doesn't exist. Docs are how users interact with your system.
Tokens are Contracts
Design tokens are the API of your visual language. Changes break consumers.
Design Tokens
Token Hierarchy
Global → Semantic → Component
/* Global: raw values */
--color-blue-500: #3b82f6;
--space-4: 16px;
--font-size-base: 16px;
/* Semantic: purpose-driven aliases */
--color-primary: var(--color-blue-500);
--space-component: var(--space-4);
--font-size-body: var(--font-size-base);
/* Component: specific usage */
--button-padding: var(--space-component);
--button-color: var(--color-primary);
--button-font-size: var(--font-size-body);
Token Categories
--color-gray-{50-900}
--color-primary
--color-success
--color-warning
--color-error
{-}
{sans,mono}
{xs,sm,base,lg,xl,xl,xl,xl}
{,medium,semibold,bold}
{tight,,relaxed}
{sm,md,lg,xl,full}
{,}
{sm,md,lg,xl}
{instant,fast,,slow}
{in,out,in-out}