- From: Jina Anne via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Sep 2021 22:37:22 +0000
- To: public-design-tokens-log@w3.org
@blackfalcon I'm not 100% sure what you mean by "the lib" (the token output? the framework you're importing them in?) As aligned with our mission objectives, we want to be **extensible**. Design tokens are also meant to be agnostic so that they can be usable by various libs and tools. Part of our goal is to give design tools/vendors a way to integrate tokens in a predictable way that makes sense and has agreement with the community. This was a big motivator in why we established this community group in the first place. Types seem necessary to make this work. And in terms of the "lib", if you mean your design system codebase, how are you documenting that? I find that types being required help display tokens in the appropriate way in the docs (colors vs units vs whatever else). Additionally, when using JS/TypeScript or other languages beyond CSS/Sass, I've found it can be very useful for linting/testing/validation (which hopefully you're doing!) and testing certain attributes for accessibility. I think from a standards perspective, as long as you can define them globally so you don't have to do each individual token (which seemed to be one of your concerns in your original comment), that this shouldn't be too inconvenient to support? Not sure I'd find this "inappropriate"? :) -- GitHub Notification of comment by jina Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/63#issuecomment-916487630 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 September 2021 22:37:24 UTC