- From: Lukas Oppermann via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Oct 2020 09:10:03 +0000
- To: public-design-tokens-log@w3.org
> I might be an odd one out designer myself but I do not believe the actual / real world token definition should exist within design software, it feels like there is not enough visibility of the impact that a token change will have in production. As tokens don't usually change very often it feels like the design software should be a proving ground for the change but not be the actual trigger for change. > Therefore I would prefer design software to be more accepting of coded token packages. For example we can provide colour tokens to Figma from the same source of truth as development through a custom plugin, however tokens like "space" seem very hard to translate as the software has a different concept of space. While I don't necessarily agree with the consequence of not allowing design tokens to be defined in the design software, I feel your concern as well. I would rather solve this with token specific library files that only certain people who "own" the design system can update. The other two points I totally agree with. -- GitHub Notification of comment by lukasoppermann Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/43#issuecomment-707605710 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 13 October 2020 09:10:05 UTC