DESIGN SYSTEM
The design system at / documents theme tokens, reusable components and the checks that cover them.
- COMPONENTS
- 11
- RSC
- 10
- A11Y
- 100
- WCAG_2.2
- AA
Sections
- Tokens · Color palette, type scale, spacing, motion, layers
- Components · 11 design-system components and the docs CopyButton helper
- Enforcement · Lint rules, CI gates, contributing guide
- Changelog · Token and component change log
- Foundations · Colors, Typography, Spacing and borders
- Primitives · one page per component where a dedicated page exists (props, variants, accessibility), listed in the page menu;
NavItemandPanelare documented in the Components gallery only
Principles
Utilities over raw values. Components reference Tailwind utilities backed by the @theme palette (text-primary-500, border-primary-subtle), never raw hex. The single @theme block in theme. is the one place a colour changes.
Server components by default. Ten components have no client directive. Field is a client component (it generates ids with useId) imported from @/; it is not exported by the main barrel, and neither is BrandIcon, which BrandLink imports by path. The docs add a client CopyButton helper for clipboard access. Server-compatible components can still enter a client bundle when imported across a client boundary.
Measured in CI. Contrast, token-boundary and component-heading checks run in quality-fast. The path-filtered performance job runs axe-core and Lighthouse on every page in the menu with an accessibility target of 100. The target is a configured assertion, not a live score on this page. The Enforcement page lists every gate.
Opinion 07: design systems
DS Framework-agnostic design systems lose unless the contract is shipping, not theory.
Web Components only pay off when you have >1 framework consuming them in production. Otherwise you bought distribution overhead to solve a problem you don't have. Stencil at Betsson worked because Angular, React, and Ember were all actually downstream, not because someone read a blog post.