- From: Matthias Dunker via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Jan 2024 10:35:08 +0000
- To: public-design-tokens-log@w3.org
> Plus, imo, Design Tokens are going to scale in purpose, but their core feature is to attempt to “describe the visual aspects, attributes and presentation of your design system” —- in that regard, with over 3000 properties (most with common sense names), CSS and the box model do a pretty good job of defining an understandable and common vocabulary to describe a component’s visual attributes (regardless of platform). 🤷🏻 I wonder who the target group of the design tokens will be. Is it okay to be more professional and therefore more precise in the naming, which leaves more room for interpretation and will make it easier for translation tools? Is it up to the design tools to present the right UI for their target group? Design tokens are the technical stuff in the background, right? Or is the idea that people will use design tokens end-to-end? I think this is quite ambitious. -- GitHub Notification of comment by MatthiasDunker Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/102#issuecomment-1886820659 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 11 January 2024 10:35:10 UTC