- From: Drew Powers via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Jan 2022 16:15:59 +0000
- To: public-design-tokens-log@w3.org
I like this idea, and this is something my team could use as well! Our color palette is broken down into a few related subgroups (`brand`, `brand-secondary`, etc.). While one opinion would be to just make each subgroup a different group in tokens (`color.brand`, `color.brand-secondary`), that seems a little unnecessary because there are no conflicts with color names, and in our code using `color.teal` is more intuitive/more efficient than `color.brand-secondary.teal`. This is an area where the subgroups feel more like a tag because they’re not necessarily a hard categorization. And to your point it’d futureproof the schema, being able to change a tag not affecting the token ID and cascading into code changes just because you wanted to associate a few colors together in a new way. -- GitHub Notification of comment by drwpow Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/109#issuecomment-1023393884 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 January 2022 16:16:01 UTC