Specify 2.0 - Your design token engine

@antonikozelski Wow, thank you so much, Antoni! 🫶

@nuno_ms_reis Thanks, Nuno!

Hi @zayan_riyaz Thank you so much for your kind words. We started by creating a design token format that included features like aliases, modes, groups, and collections. - Aliases to be able to create references between tokens and to allow create a reference for a particular part of a token. For example, to be able to alias only the color of the border and keep the rest of the values absolute. - Group to allow organizing tokens by folder. So you can use group to group your tokens by semantic, platform, brand… It’s very flexible. And aliases are independent from the groups. It means you can create aliases between tokens in different groups. - Modes are useful to define different values using an external context, like color themes or different devices. Modes are defined by tokens… … and they can be used in a collection to validate that all tokens in a collection include all the modes described in the collection. It means that if you consume a collection to generate your themes light and dark, you are sure that each token has value for each theme. We continued the development by creating a convertor between Figma and Specify to generate all tokens in seconds. And we complete the product by creating an SDK, an API, and integration with GitHub that leverages our transforms to generate any kind of code. In conclusion, we provide a list of tools and features to do what you want with your design tokens.

@daniela_muntyan Thank you, Daniela!

@rawrjays Thank you very much! If you have any feedback, please do not hesitate to share it :)

@glorian_mariyapnooor Thank you so much! :)