- From: Martin \ <sysbot+gh@w3.org>
- Date: Thu, 16 Jul 2020 11:59:44 +0000
- To: public-design-tokens-log@w3.org
That sounds good, and actually there are print-related design tokens that would benefit from the media scoping for example. (As an aside CSS also will have nesting anyway btw: https://drafts.csswg.org/css-nesting/) Use of keywords in place of element selectors would be good to think more about on. Being able to more innately link variables from other tokens at a native syntax level would probably be a big win as that is the weakness of CSS that was making it really hard to argue for it. JSON on one hand has awesome nesting and variable access in languages, but harder to write and doesn't do much. CSS being flexible and easy to update but doesn't lend itself to reusability (css variables sorta helps but it's a bit late). So a combination of JSON and CSS is probably the best here. I think @oscarotero hit a nice balance there of human readability and editing. Where in place of selectors they are keywords that can be used to access the tokens in that group. Would being strict about standardised keywords instead of user-defined names mean that the file is flatter and thus better as a universal format? (Namespacing can still be done at a filesystem-level mind you) -- GitHub Notification of comment by Martin-Pitt Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/1#issuecomment-659364476 using your GitHub account
Received on Thursday, 16 July 2020 11:59:46 UTC