Roadmap
Changelog

Have a request? Something unexpected happening?

We'd love to know what you are thinking, seeing or expecting.

❇️ Per-File Preferences for Active Themes and Export Settings

The plugin currently does not remember user preferences for enabled Themes and export configurations (styles and variables) on a per-file basis. When exporting "Themes," the system defaults to enabling ALL themes, which often doesn't reflect the user's active themes in the editor view for that specific file. This forces users to manually deselect unwanted themes repeatedly for each file, which is time-consuming and increases the risk of exporting incorrect assets, especially when managing multiple files with distinct theme and export requirements. Proposed Solution: Implement a system that saves and automatically applies preferences for each individual file. These preferences should include: β€’ The selection of enabled/active Themes within the editor and for export. β€’ The configuration of which specific styles and variables are marked for export. This way, when a user opens a file, their previously used settings for that file are automatically restored.

Nathalie D About 1 month ago

1

❇️ Plugin UI Enhancements

Parts of the plugin that could still use some UI improvement Requested Import Variable Features to support: The Styles&Variables button in the plugin is not properly aligned to the pixel grid, causing it to appear larger and slightly blurred. This misalignment is noticeable under the New Set button, which might also be shifted slightly. Proposed solution: Adjust the alignment of the Styles and Variables button to the pixel grid. Consider setting the default size of the left sidebar to ensure proper alignment with the button, enhancing visual consistency and clarity. 😬 The reality πŸ’­ How might we... πŸ’¬ Feedback that is valuable How does this issue impact your day-to-day workflow? What workarounds do you have? What other typography features would be helpful to your projects? ↔ Related topics TBD β†’ Jump to post TBD β†’ Jump to post

Keegan (Tokens Studio) 3 months ago

πŸ’¬ Discussion

W3C DTCG Spec - Unofficial Token Types

Tokens Studio has several independent Token Types that are not officially recognized in the W3C DTCG Specifications: Spacing Sizing Border Width Border Radius The spec defines a Dimension Token as the preferred type for these properties. If we want to fully align with the spec, Tokens Studio is required to phase out these β€˜unofficial’ Token Types. However, we believe the choice should be yours! We have a custom transformation that changes these Token Types to dimension included in the SD-Transforms npm package and we’ve introduced a dimension as its own Token Type. Feedback that is helpful How does having these properties as independent Token Types influence your workflow? What would the impact be if these Token Types would be deprecated, assuming migration was taken care of by Tokens Studio?

Sam - Tokens Studio 5 months ago

πŸ’‘ Requests

Deprecate Composition Token Type

The Composition Token is a Token Type we initially introduced to support design decisions that are typically composed of multiple parts, like typography, shadows and borders. Since then, a lot has changed. The Design Tokens Community Group hosts a token specification on the W3C community group pages for web standards. Although it's in draft form, the tools and technologies working with Design Tokens are trying to align with the W3C DTCG specification. The W3C DTCG specification defines each of these composite design decisions as their own Token Type instead of a generic composition Token Type. β†’ See the W3C DTCG Spec 9.0 Composite types for more details You might have noticed Tokens Studio is aligning to the W3C DTCG spec by introducing as many of the same Token Types as reasonable and feasible. We now support typography, border, and boxShadow as independent Composite Token Types. Migrate away from using the Composition Token Type in the plugin when possible We encourage our community to migrate from using the 'legacy' composition Token Type to a corresponding official token type, as we may deprecate it in the future. An engineer working on Style Dictionary has also formally requested we deprecate this Token Type due to its problematic nature in code. (Github 2800) Could it be a feature in Tokens Studio instead of a Token Type? We know some of you love the idea of Composition Tokens as a way to have a single token which captures the values of as many design decisions as possible applied to a component. In fact, many of you have requested features to push this idea even further. The goal it is to work faster without having to apply so many Tokens manually. While this doesn't align with the direction of the W3C DTCG spec for a Token Type, having a feature that would allow multiple Tokens to be applied in one click could be an interesting feature the Tokens Studio team could work on in the future.

Sam - Tokens Studio 5 months ago

1

πŸ’‘ Requests

❖ πŸͺ„ Export Styles to Figma enhancements

We introduced the new ❖ πŸͺ„ Sync variables and styles is now Export to Figma in V2 of the plugin. Where you can export multiple types in the Wizard to Styles & Variables: When people are now using Variables for their colors, but want to export their Gradient to Styles (which are in the same set/theme), all colors get exported including the Gradients. It would be great if we can add another option, to export β€˜Gradientsβ€˜ separate from β€˜Colorsβ€˜ Requested Export Styles: Add extra option, to export β€˜Gradientsβ€˜ separate from β€˜Colorsβ€˜

Tokens Studio Team 5 months ago

πŸ’‘ Requests

πŸ” ❇️ Import Variable Enhancements

With some part of our community uses import variables, they have expressed some enhancements to improve their workflow: Requested Import Variable Features to support: Import Variables should include Themes [Pro] Currently when importing variables, collections and modes are translated to sets and subsets and don’t include the plugin’s Themes. We might want to support this as exporting variables translates theme-groups and themes (for pro users) to Figma’s variable collections and modes. Selective Import of Variable Modes When importing variables into the plugin, it’s good to have the ability to select which variable modes will be imported. This would provide greater control and flexibility during the import process, allowing users to tailor the import to their specific needs. Importing Typography Variables Loader / Indicator for Importing Variables Import Variables in Order Created Also Import (update) Deleted Modes or Collections 😬 The reality πŸ’­ How might we... πŸ’¬ Feedback that is valuable How does this issue impact your day-to-day workflow? What workarounds do you have? What other typography features would be helpful to your projects? ↔ Related topics TBD β†’ Jump to post TBD β†’ Jump to post

Tokens Studio Team 6 months ago

3

Refresh Git Branch Status Without Restarting Tokens Studio

Current Flow when a Git branch is deleted (e.g., after a merge), it still appears in Tokens Studio until the plugin is closed and reopened. This behavior affects the usability of all syncing providers that use branching, including GitHub, GitLab, Azure DevOps (ADO), and Bitbucket. User Feedback It would be helpful to have a β€œRefresh” button or an automatic refresh feature in Tokens Studio that updates the Git branch status without requiring a restart. This feature would detect changes in branch availability (e.g., deletions or updates) across all supported syncing providers, ensuring the interface accurately reflects the current state of the repository. This enhancement would streamline workflows and reduce the need for repetitive manual actions.

Nuthan (Tokens Studio) 6 months ago

πŸ’‘ Requests

Plugin Tokens Tab - UI Affordance to collapse/expand groups

On the Tokens Page of the plugin - ideally there would be a single click operation to expand or collapse all branches created by Token Groups. It’s very inconvenient when working with large trees - It’s a lot of manual effort to close all parent groups until the one that is needed is reached. A keyboard shortcut could work (for example [CMD], [SHIFT] + click on a node) and automatically collapse all others.

Π”ΠΌΠΈΡ‚Ρ€ΠΈΠΉ ΠΠ»ΡŒΠ±Π΅Ρ€Ρ‚ 6 months ago

2

Exporting to Figma causes all Figma variables to be republished

If I change one thing in Token Studios (bye it add a new token, delete a token, edit a token name or value) and then export Variables & styles to Figma, when I publish the Figma library, Figma thinks that every variable and style (and therefore everyone connected component) has been modified and republishes everything This creates issues when you want to adjust one component’s token and publish just that token, whilst also having other tokens and components in the file that are not ready. It also has the issue of making the Figma publication very slow (for a decent sized library) The screenshots attached were the result of updating one existing token value and exporting to Figma (the library prior to this had been full published and had no outstanding items to publish)

Chris Kerr 10 months ago

1

✨ Improve UI of Recover local changes Modal

Current Functionality When you exit the plugin with changes in your local configuration vs what is stored in your repo, you get this warning message to either use the local ones or pull down from the repo and discard the local changes: User feedback - the button copy could be more explicit. Although β€œYes” ties into the title, it doesn’t work quite as well grammatically with the modal body content. Given this is also a potentially destructive change if you hit β€œCancel”, it might be better using a danger/destructive semantic:

Keegan (Tokens Studio) 10 months ago

πŸ”€ Show Updated Number When Exporting Variables with Updated Values

Currently when you have existing Figma collections and export new values, the toast either shows "No Variables Created" as of rc10 or "3 collections and 120 variables created" in 38.9. πŸ’­ How Might We It would be good to count the variables that are updated, separate from those created. rc10: 38.9

Keegan (Tokens Studio) 10 months ago

πŸ’‘ Requests

πŸ§‘πŸ½β€πŸ’» Import Read-only Token-set + add local token sets

βž• Feature Request User would like the ability to pull read-only token set from a syncing provider. This system would allow the import of token sets in a read-only format, similar to how one would use β€˜import in CSS’. Additionally, the user would like to have the capability to define local sets that can override some of the values from the imported token sets. Local Overrides: β€’ Users should have the ability to define local token sets that can override specific values from the imported token sets. β€’ This feature should enable customization and extension of the imported tokens without modifying the original imported values.

Keegan (Tokens Studio) 10 months ago

πŸ’‘ Requests

View node count more effectively

As I am working on restructuring a design system with tokens in Figma I would love to have a simpler way to see the node count in a more effective, less intrusive, way. And if it was possible for an even sexier option, a way to show + export those stats per section/page/file basis. If there is a function already, please let me know! ❀

Dennis Buizert 10 months ago

1