- From: Donnie D'Amato via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 May 2023 17:38:30 +0000
- To: public-design-tokens-log@w3.org
> For us, having distinct files would be unmanageable. We define hundreds and hundreds of tokens, currently with 18 different modes applied. Getting the full picture of what a token's value can be would be difficult, and we find that once the token system is set up, we update _tokens_ rather than updating modes. Having a single file where a token showcases all its values make that easier to manage. > > I'd love to see both formats supported by tools, though I believe what tools like Style Dictionary currently do (multiple files with a value per token per file) is too inconvenient for long-term maintenance workflows. @Sidnioulz could you describe your curation process a bit further? Also what purpose does seeing a token's value across themes provide? From my perspective, token values curated collectively by theme reduces context switching across themes because we commonly select values for tokens related to other existing values in the same theme. Seeing the token value across themes out of context of the larger theme doesn't seem helpful but I'm interested to know how it could be? -- GitHub Notification of comment by ddamato Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/210#issuecomment-1553396753 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 18 May 2023 17:38:32 UTC