🪄 👩‍💻 JSON Enhancements

The V2 release supports a new Token Format or the way the design tokens are written in their JSON files, as we move towards alignment with the W3C Design Tokens Community Group Specification.

When the plugin is set to:

• Legacy (token) Format

  • the JSON files will not be modified.

• W3C DTCG (token) Format

  • The JSON files will be converted according to

    • ❇️ W3C - DTCG Specification Alignment → Jump to post

You might also notice some cosmetic changes:

• a new UI Affordance to access the JSON editor view in the top right of the plugin

• a more colorful JSON editing experience

🐛 Known issue being fixed

• "With the work on W3C we introduced a change which seems to cause a different order in tokens of our users. Existing .json files seem to have changed the order of individual keys. Technically not a big issue as this is just relevant to the individual keys (value, type, description and so on), but we don't want to be changing user's files without much reason." - Github #2653

Related items

• ❇️ W3C - DTCG Specification Alignment → Jump to post

• ❇️ DTCG W3C | Token Group Metadata - Description and Type → Jump to post