- From: Drew Powers via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Jan 2022 21:41:46 +0000
- To: public-design-tokens-log@w3.org
Yes there’s definitely a lot of overlap with #97 for sure. And to your point, organizing by groups does let you use both tokens at once, which you may want. That flexibility is a good thing. But there’s also times at which I not only want a _guarantee_ that variants of a certain thing exist, but also want to restrict certain things from being used together. For example, if I have `theme-dark-active`, I need to also make sure that `theme-light-active` and `theme-colorblind-active` exist, and it would be a lot of work to keep all these in sync. And I want to also ensure those palettes are never used together (e.g. when in colorblind mode, enforce colorblind-friendly palettes). So for that reason I like to call it “modes,” which only apply to a group. A theme is therefore merely a collection of “modes.” Again, I could do this with groups, but keeping all these themes synced is just a lot of work either manually or by building tooling. And I selfishly just want the schema to take care of that for me 😄 -- GitHub Notification of comment by drwpow Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/2#issuecomment-1012538070 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 13 January 2022 21:41:48 UTC