- From: Carlos Araya via GitHub <sysbot+gh@w3.org>
- Date: Sat, 15 Apr 2023 22:15:54 +0000
- To: public-design-tokens-log@w3.org
I think the typography type is trying to do too much. There are multiple areas we can split the current implementation in a way that would be easier to use and easier to reason through without having to go through every single CSS property and its equivalent in design tools that consume the tokens. I'm also assuming that if a tool cannot use a given property, it will ignore it The ones that come to mind off the top of my head: * `font-declaration`: Equivalent to CSS font-face at-rule and its associated attributes (see [MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face)). Since the values are specific to a font, I think it's good to create a composite token * `font-layout`: line height, font-kerning, letter spacing, word spacing, text indentation. These values are more dependent on the design of content so they should be more flexible or open -- GitHub Notification of comment by caraya Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/102#issuecomment-1509988828 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 15 April 2023 22:15:55 UTC