Design System Governance
Freeze design tokens and component contracts, trace alias changes and measure implementation markup against released style and usage rules.
Application guideVerifying your session…
Using Design System Governance
Govern released component specifications and review their implementation against token and usage contracts.
Token aliases · Versioned specifications · Rendered conformance
- Inputs and working data
- Typed design tokens and aliases, component specifications and rules, immutable release snapshots, supplied HTML/CSS and measured browser evidence.
- Working in the editor
- Token library, component usage contracts, release diff and sandboxed browser measurement for marked component instances.
- What can I produce?
- Versioned CSS tokens and component/review JSON with instance-level expected and observed results.
- What are the limits?
- 250 tokens, 100 component specs, 30 releases, 100 reviews, 60 measured instances per review. Pixel lengths, opaque colours, scalar opacity and durations.
- Example
- Release a component colour and text rule, inspect compliant and noncompliant specimens in a real browser, and restore the reviewed release.