- From: Mattia Astorino via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Nov 2022 19:56:42 +0000
- To: public-design-tokens-log@w3.org
Speaking about design tokens core principles, aliases (aka themes) don't share the same principles like being the source of truth across the system.
If product A uses `color-500: #ff00ff` and product B uses `color-500: #00ff00`, then that principle is broken; tokens are not consistent anymore, and they become unpredictable across the system.
That’s why aliases/themes are useful; their value can change across the system and implementation: Product A can use a theme with `link-color: {color.500}.`, while product B can use another theme with the same key but different value, like `link-color: {color.200}`. And avoid breaking that token principle.
So, using the same name for different things seems confusing. We say design tokens are the single source of truth, but we show “tokens” changing values across usages.
If it is only I who finds this confusing ok. But naming is essential in this phase.
--
GitHub Notification of comment by equinusocio
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/187#issuecomment-1325588101 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 November 2022 19:56:44 UTC