- From: Drew Powers via GitHub <sysbot+gh@w3.org>
- Date: Thu, 24 Feb 2022 16:34:14 +0000
- To: public-design-tokens-log@w3.org
drwpow has just created a new issue for https://github.com/design-tokens/community-group: == $name property? == In our tokens schema we make use of `$description`, but could also use a human-readable `$name` as well. For one example: ```json { "typography": { "brand": { "$name": "Brand Typography", "$description": "Typographic styles for marketing and promotional material", "heading1": … "ui": { "$name": "UI Typography", "$description": "Typographic styles for UI", "heading1": … } } ``` Having the `$name` is able to preserve a human-readable name that wouldn’t be preserved in the token ID alone, or it would otherwise be awkward or redundant. In the format examples, there are token IDs like `"Button background"`, which _are_ human readable, but when used in context would generate an ID like `actions.button["Button background"]` which are a bit verbose. Would there be a use for an optional `$name` property that allows tokens to have a friendlier name than their ID? (keeping in mind this, and any other property, may live in `$extensions`; just wanted to discuss if this is generally useful for others or not) Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/112 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 24 February 2022 16:34:16 UTC