Practitioner token views
These files are generated from the normalized JSON extracts in the parent directory. They provide a readable summary for design-system practitioners and embed the authoritative raw JSON for auditability.
After changing a JSON extract or manifest.json, run powershell.exe -NoProfile -ExecutionPolicy Bypass -File ..\render-markdown.ps1 from this directory, or the equivalent command with .\render-markdown.ps1 from token-library/. Do not edit generated system pages by hand.
| System | Model | Public token coverage | Practitioner view | JSON |
|---|---|---|---|---|
| Adobe Spectrum | global platform scale plus component-local density | high | View | JSON |
| Angular Material | numeric theme density with component-specific clamps | high | View | JSON |
| IBM Carbon | component size variants; density is not a global product mode | high for component size metrics | View | JSON |
| Microsoft Fluent 2 React | component-local size props over a shared spacing/type foundation | high for inspected components | View | JSON |
| PatternFly 6 | component-local compact modifiers remap component custom properties | high for compact-enabled components | View | JSON |
| Salesforce Lightning Design System | compact semantic alias remapping plus record-form layout choices | medium; production resolver private | View | JSON |
| SAP Fiori / UI5 Web Components | inherited cozy/compact content-density context with component custom properties | medium; global theme package external | View | JSON |
| Meridian | scoped inherited density variables plus explicit component sizes and a local table modifier | high | View | JSON |
| SAS design-system density case study | independent density collection in a multi-axis token pipeline | low; production package unavailable | View | JSON |
| Uber design-system density demo | component-specific Figma variable collection inherited from a frame | limited to visible List Item collection | View | JSON |
How to use these views
- Read the architecture model and activation mechanism before comparing values.
- Treat component size APIs and inherited density modes as different mechanisms unless the source connects them.
- Check the evidence gaps before treating a missing value as an invariant.
- Use the embedded JSON to audit field-level detail or supply structured context to another tool.
- Do not copy external-system values into PDS without the PDS component audit and accessibility validation.