Several teams where asking to be able to automatically generate a theme compatible with the theme-ui specification.
That's why, we're thrilled to present you the to-theme-ui parser.
The Theme-UI specification closely looks like another famous CSS utility-first framework. We let you guess on which parser we're currently working on 🌬
The link-design-tokens parser helps you link color and measurement design tokens to complex ones like gradients, borders, shadows or text styles.
It replaces absolute values by their potential corresponding design token.
This parser is especially useful when used before the to-theme-ui parser.
Finally, the new replace-string parser helps you replace any string matched by a regex by a new string.
Let's say you have some a color named "Red" in your Figma local styles in a "Colors" folder. The color name returned by Figma is "Colors / Red".
This parser helps you rename your design tokens without characters before the last slash:
- Before: "Colors / Red"
- After: "Red"
- You can now extract gradient and radius from border design tokens.
- We previously ordered tokens alphabetically. Tokens are now ordered in a more natural way. For example, given the colors "Carbon 40, Carbon 5, Carbon 50" it now gets listed as "Carbon 5, Carbon 40, Carbon 50".
- When you delete your user, the Github connection associated to your account will also be deleted.
- Fixed the font file conversion to the
We've recently been working on improving the overall navigation experience inside a repository. We started by making changes to the repository sidebar.
In this new release, we also improved the category management experience. Many of you were asking for a way to hide empty categories. We listened and from now on your repositories will by empty by default. You will then be able to create new categories.
- Improve the CLI's version checking by doing a synchronous check when options
Getting a first convincing experience as a user when trying a service is always valuable. We've always wanted you to be able to understand Specify's design API concept as easily as possible. This is why we've been working hard on improving your first minutes of usage inside Specify lately. The onboarding first iteration was satisfying but still could be improved in several ways.
This onboarding new iteration includes the following improvements:
- When connecting Figma as your first source application, the Figma details panel will be open by default. It makes you one click away from your first source installation.
- Some steps now includes links to articles from our Help Center.
- After completing certain steps you'll be automatically redirected to the onboarding. This will help you complete it more easily.
- You can now go back to completed steps.
- We've added another step to help you connect Github as your first destination application.
- The onboarding widget is now displayed on every page of the app.
You've been asking for more control over number values returned by the API. We listened and we added the round-number parser.
If you ever synchronized design tokens from Figma and saw that some values should be rounded this parser is for you. No one needs a line-height of
17.096544px or a letter spacing of
0.579px. This parser will help you fix this.
- Add warning message when imported font files don't match the missing font files.
- Fix login error on slow network conditions.
- Fix a bug where the svgo parser removed many properties on asset files. You can now use it properly with the name-assets-files-by-pattern parser.
- We've improved the content writing experience in modals. Your content will be saved until you submit it or open a new modal.
We recently revamped the overall navigation within the application. More precisely, we had to revamp the navigation inside a repository to prepare future page additions. We're glad to say goodbye to the Tabs pattern we were using. Your repository settings and its connected destinations are now available directly from the sidebar. This will allow us to easily add new pages in the future, like Sources for instance.
Also, following some feedback from our users, we've improved the legibility of your repository design tokens and assets by framing the table.
- Modals can now be closed with the
- Fixed the loading of text styles when a new font or text style was added
- Fixed a loop when loading a repository where you ended up on a 404 page without being able to leave it without refreshing the page
We've added more information about the applications you've connected to your organisation. This will help you see:
- From which account your design tokens and assets are coming from
- To which account they are distributed to
This parser will help you name your assets exactly the way you want.
To give you an example, at Specify we use it to:
- Name our SVG icons after optimising them with the SVGO parser:
- Add resolution data into our bitmap's filename:
Up until now, you could only synchronize a category within a repository. Now you can also choose to sync the whole repository at once.
We've added an onboarding to help first users understand how Specify works. It guides you from your first source connection to your first destination connection. After this, Specify won't hold any secrets for you anymore!
- [Assets] We've added support for PDF assets. Teams targeting iOS applications, this is for you!
You've been waiting for it and here it is! You can now extract your fonts and your text styles from your Figma documents.
This parser generates CSS
@font-face rules for your font. No more manual font import in your project 💪
This parser generates your text styles in CSS classes.
This parser generates your text styles in SCSS mixins.
From now on you can generate a DSP with Specify. A DSP is a package with a specific format that allows you to transit your design data with every tool compatible with this specific format. Such as Adobe XD or Visual Studio Code. Learn more on the DSP parser.
This parser allows you to set a suffix to string. Here are a few examples:
- Append an extension at the end of a filename
- Append a custom string at the end of a design token name
- [Gradient] Add the possibility to extract gradients from Figma's local styles
- [Color] Fix a bug where colors couldn't be pushed if there is a gradient within the local style
- [Ui] Fixed and improved some components
We've added a full documentation page regarding our integration with GitHub. It helps you understand how you can sync your design tokens between your Specify and Github repositories.
You can now filter several design token types at once. In the configuration file the
types property is now an
- [Doc] Fix the supported token list
- [Doc] Fix a bug where the documentation theme do not follow the app one
- [Doc] Fix some inconsistencies in the wording
- [App] Add an icon next to the error message
- [App] Update on the get started page
- [GitHub] The GitHub app can be installed on another branch than master
We've added the command
specify sync to synchronize a targeted repository in your config file.
We've added the command
specify --help or
specify -h to access to the Help interface in the CLI.
- [App] Update button within the feedback modal
- [App] Fix a bug where the app theme do not follow your choice
- [Login] Fix the error icon in Dark mode
- [Doc] Add a list of token supported by Specify
- [Doc] The app theme choice will now impact the documentation one
- [Doc] Fix a bug where the theme selector in the documentation do not trigger the right theme properly