While working on size & spacing tokens, the question about when to refer to theme option values was raised:
Both, codex-base and codex-components should reference theme option tokens for traceability. What decision is pointing back to which token out of the option pool.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Duplicate | • STH | T302348 <Platform Initiative> Release Codex in Beta (Limited Production Release) | |||
| Invalid | None | T302025 Upgrade Codex to Beta version | |||
| Resolved | Volker_E | T293127 [EPIC] Design System Foundation: Design and define design tokens | |||
| Invalid | Volker_E | T321738 Refine token implementation guidelines to reflect theme option to decision tokens clearer |
The component tokens are already documented as applying theme-agnostic named tokens. This tasks seems not further workable.