Changelog

Changelog

Changelog

Changelog

Find out about Specify latest product changes.

Find out about Specify latest product changes.

Find out about Specify latest product changes.

Find out about Specify latest product changes.

Improved naming system for your vectors

In Figma, you can create icons as regular layers or as components with variants. This release will benefit teams using Figma components for their icons system.

From now on, Specify will name your icons after your variants name and their respective order in Figma. It means that if you rename your variants or reorder them, their name will also be updated in Specify.

A better naming convention leads to better alignment ๐Ÿ’ช


Parser update: To Tailwind

We've also improved our to-tailwind parser. This update helps you control the name of all your design tokens per type. Tailwind will use those renamed design tokens to generate your utility classes.

๐Ÿ‘‰ See our updated configuration example

This improvement prevents you from getting potential collisions between utility classes generated by Tailwind.

Want to learn more about this improvement? Jump in the dedicated GitHub discussion.


Bug fixes & improvements

  • You can now refresh design tokens and assets detected by Specify in your Figma files when creating or updating a source

  • Added several links to help you create a personal access token in Specify's documentation

  • Fixed a bug that prevented the creation of multiple sources for the same type of design token or asset

Improved naming system for your vectors

In Figma, you can create icons as regular layers or as components with variants. This release will benefit teams using Figma components for their icons system.

From now on, Specify will name your icons after your variants name and their respective order in Figma. It means that if you rename your variants or reorder them, their name will also be updated in Specify.

A better naming convention leads to better alignment ๐Ÿ’ช


Parser update: To Tailwind

We've also improved our to-tailwind parser. This update helps you control the name of all your design tokens per type. Tailwind will use those renamed design tokens to generate your utility classes.

๐Ÿ‘‰ See our updated configuration example

This improvement prevents you from getting potential collisions between utility classes generated by Tailwind.

Want to learn more about this improvement? Jump in the dedicated GitHub discussion.


Bug fixes & improvements

  • You can now refresh design tokens and assets detected by Specify in your Figma files when creating or updating a source

  • Added several links to help you create a personal access token in Specify's documentation

  • Fixed a bug that prevented the creation of multiple sources for the same type of design token or asset

Improved naming system for your vectors

In Figma, you can create icons as regular layers or as components with variants. This release will benefit teams using Figma components for their icons system.

From now on, Specify will name your icons after your variants name and their respective order in Figma. It means that if you rename your variants or reorder them, their name will also be updated in Specify.

A better naming convention leads to better alignment ๐Ÿ’ช


Parser update: To Tailwind

We've also improved our to-tailwind parser. This update helps you control the name of all your design tokens per type. Tailwind will use those renamed design tokens to generate your utility classes.

๐Ÿ‘‰ See our updated configuration example

This improvement prevents you from getting potential collisions between utility classes generated by Tailwind.

Want to learn more about this improvement? Jump in the dedicated GitHub discussion.


Bug fixes & improvements

  • You can now refresh design tokens and assets detected by Specify in your Figma files when creating or updating a source

  • Added several links to help you create a personal access token in Specify's documentation

  • Fixed a bug that prevented the creation of multiple sources for the same type of design token or asset

Improved naming system for your vectors

In Figma, you can create icons as regular layers or as components with variants. This release will benefit teams using Figma components for their icons system.

From now on, Specify will name your icons after your variants name and their respective order in Figma. It means that if you rename your variants or reorder them, their name will also be updated in Specify.

A better naming convention leads to better alignment ๐Ÿ’ช


Parser update: To Tailwind

We've also improved our to-tailwind parser. This update helps you control the name of all your design tokens per type. Tailwind will use those renamed design tokens to generate your utility classes.

๐Ÿ‘‰ See our updated configuration example

This improvement prevents you from getting potential collisions between utility classes generated by Tailwind.

Want to learn more about this improvement? Jump in the dedicated GitHub discussion.


Bug fixes & improvements

  • You can now refresh design tokens and assets detected by Specify in your Figma files when creating or updating a source

  • Added several links to help you create a personal access token in Specify's documentation

  • Fixed a bug that prevented the creation of multiple sources for the same type of design token or asset

Start automating your design system today