Call to read the First Public Editor’s Draft and share feedback
Posted on:Over the past several months, the team collaborated with multiple design tool vendors to draft the format module of the Design Tokens specification.
We’re now inviting everyone in the community to read the First Public Editor’s Draft and join the conversation on GitHub.
Thanks to everyone in the community and to all vendors who helped in reaching this milestone. We can’t wait to keep working with you and build the future of design tokens together!
What’s next?
- Editors will compile community feedback and work to reach a consensus on every issue that’s been raised. Expect the draft to change a lot during this step.
- Once critical issues are solved, we’ll publish a First Working Draft. Expect rare edits to normative sections of the Working Draft. At this stage, the specification can be used to build implementations. We’ll be collecting more feedback from vendors, tool developers, plugins/extension developers.
- Once multiple vendors have implementations that follow the Working Draft, we’ll move to Final Specification.
During steps 2 and 3, the W3C will review the reports to exclude any risk of intellectual property infringement.
In parallel, we’ll work on other modules that depend on the Format Module, such as Colors, Motion, Typography.
I realize the DT specifications are still being fully vetted, but, I’m wondering if there are any implementations being developed in the open? I was discussing design token compatibility on the open props GitHub repo: https://github.com/argyleink/open-props/discussions/87 and this recently released open source library seems like it could be a nice addition (sort of tailwind via css custom properties). But, I think switching from .js files to JSON and making it compatible with the design tokens specification would be ideal. I’m not an AST specialist, and I’d assume some of these vendors listed have folks that are; and a JSON to AST to other formats approach is probably ideal. If such tooling is evolving, is there a list? It would be nice to attempt to wire up open properties to such a tool and see if it could be refactored to be design tokens compliant.
Hi Rob,
Apologies for the delay in response. Can you post this on the community group’s issues board? That is where we do all of our discussions publicly. https://github.com/design-tokens/community-group/issues
Thanks!
Pingback: Call to implement the Second Editors’ Draft and share feedback | Design Tokens Community Group