You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After taking a look, there are a few awesome changes that I was excited to see!
May I suggest adding a link to the July 2023 updated version of the draft from the home page? For folks who care enough to try and learn about tokens from the DTCG, it would be nice to have easy access to the most recent information.
Thanks for all your hard work! 🫶
The text was updated successfully, but these errors were encountered:
Good shout. We should probably make that clearer. In my mind, the spec at https://tr.designtokens.org/format/ is a kind of living draft. Whenever we merge PRs, the spec there updates.
The 1st & 2nd editors drafts on the other hand are fixed snapshots, that will never change again. I expect we'll cut further snapshots from time to time (FYI, there was some debate amongst the editors a while ago about whether there'd be another "editor's draft" snapshot, or if we'd go straight to a v1 spec next).
On a related note, something I've been thinking about adding recently is some kind of changelog (perhaps as an appendix to the spec?). We could explicitly state what's been added or changed since the last snapshot. Do folks feel that would be helpful?
I was assuming that there were no updates to the draft of the spec, as the home page on the W3C community group states 2022 as the last activity.
However, I noticed when referencing the 2nd edition (for a piece of content I am working on) that there is a link to "Latest published version".
After taking a look, there are a few awesome changes that I was excited to see!
May I suggest adding a link to the July 2023 updated version of the draft from the home page? For folks who care enough to try and learn about tokens from the DTCG, it would be nice to have easy access to the most recent information.
Thanks for all your hard work! 🫶
The text was updated successfully, but these errors were encountered: