- From: Drew Powers via GitHub <noreply@w3.org>
- Date: Mon, 10 Nov 2025 15:56:17 +0000
- To: public-design-tokens-log@w3.org
@caoimghgin Yeah I think this is really just a shortcoming of material and tools on the resolver module right now :/ and I’m taking it as such. 100% understand that from an outside perspective, a lot of these things are somewhat impenetrable without additional resources right now that are lacking. We are working on guides! Thanks for bearing with us 🙇 Again, timing-wise I am talking with the Style Dictionary folks again later this month to try and work on adding support there. I’m really hoping the timeline is roughly: 1. **Specification finalized**: (where we are now) the technical details are set-in-stone so tools can start working on implementation. The specification is needed for toolmakers but is confusing/too complex for most folks 2. **Tool support**: (in progress) Style Dictionary and Terrazzo support the updated specification, unblocking folks from using it in day-to-day applications 3. **Guides/resources**: (future) unblocked by tooling, there can be better “how to” guides that are practical and approachable, not purely theoretical. We’re just on step 1 now, and have a long way to go 😓. As an aside I’d be happy to walk through the resolver more in detail at a conceptual level if you’re interested in that! I’m unsure whether it’s valuable given that tool support isn’t there yet, but just conceptually if you ever want a preview of what’s coming _later_ I’d be happy to meet! Just DM me in the Design Systems Slack. -- GitHub Notification of comment by drwpow Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/348#issuecomment-3512559830 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 10 November 2025 15:56:18 UTC