- From: Lukas Oppermann via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Mar 2021 20:25:36 +0000
- To: public-design-tokens-log@w3.org
Hey @nhoizey, thanks for all your thoughts on the topic. Concerning the `Property naming specifications` I was coming from a "tool maker" perspective (as I work on some design token tools). However the example is not that great as it does not necessarily matter so much for colors. Lets say tools like Figma and Sketch implement design tokens: 1. The user can use tokens In different places 2. The user defines multiple size / pixel based tokens: ```css border-radius--small: 4px; border-radius--default: 8px; spacer--4: 4px; spacer--8: 8px; spacer--16: 16px; ``` 3. The tool maker may want to only show the `radius` tokens for the `radius property` and the `spacer` tokens for `auto-layout` or `padding` 4. To allow this any consumer of tokens (incl. tools) must be able to "understand" the tokens. This is were naming standards would be helpful. It could also be solved by a property on the item that defines the use case (which than would probably have to be standardised). I am not saying this idea was the best solution. But having a way to "understand" values would be very helpful. -- GitHub Notification of comment by lukasoppermann Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/1#issuecomment-797025511 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 11 March 2021 20:25:39 UTC