Editors
Why colour is not selected in the CMS
DynamicWeb includes design settings for colours, fonts, and button styles. This implementation does not connect templates to those settings. The design tokens remain the source of truth.
One source of truth
Brand colours, type, and spacing live in the design tokens used by the shop, partner tools, company store, and presentations. A local CMS colour would apply to one surface only and allow the identity to drift.
Contrast is tested automatically
The current token build runs 80 contrast checks across the declared light and dark pairs. A required pair that fails WCAG AA stops the build. A local CMS colour would bypass that contract.
One active variant and two colour modes
The system currently has one active brand variant with light and dark modes. Product-line names share that system. A future variant must be defined in the token source and pass the same checks before use.
What to do instead
If you need a new colour, type role, or visual treatment, ask the design-system owner. The change belongs in the source tokens, where it can be reviewed and tested before the generated outputs are released.
Implementation reference
DynamicWeb design settings affect a template only when that template opts into them. These templates do not. The evidence and implementation details are documented in docs-dw/design-settings.md.