- From: Christopher Dura via GitHub <sysbot+gh@w3.org>
- Date: Sat, 15 Jul 2023 16:51:06 +0000
- To: public-design-tokens-log@w3.org
> Small question...why are we putting inside the spec terms that exist only inside CSS? DT are platform agnostic, they must be transformed for each platform and `web/css` could not be included. For example letter-spacing is a CSS only thing, the technical name is `kern/kerning` and for example on iOS is called `kern`, not `letterSpacing`... It seems this spec is becoming web-target-only, and so useless for a real multi-platform project (where DT really shine) I ran into this debate with letter spacing and iOS, too. However, I think the reality of the situation is that most “design system thinking” is going to “start” with the Web platform simply because it’s arguably the largest, and most popular community, so most people will likely be coming from that background, and will understand “the visual language of the Web”, aka CSS. 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. 🤷🏻 -- GitHub Notification of comment by chris-dura Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/102#issuecomment-1636823948 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 15 July 2023 16:51:07 UTC