figma-plugin icon indicating copy to clipboard operation
figma-plugin copied to clipboard

Theme Settings for Figma and Development

Open keeganedwin opened this issue 1 year ago • 5 comments

Is your feature request related to a problem? Please describe. Currently, when working with themes in GitHub, users find themselves repeatedly modifying settings to enable sets for when creating styles in Figma, and then switching them back to source for development purposes when running Style Dictionary. This process can be cumbersome and error-prone.

Describe the solution you'd like Implement a way for users to switch between Development and Figma settings which should then be applied when running Style Dictionary.

keeganedwin avatar Jul 18 '23 11:07 keeganedwin

Can you give some more context on this? Why were they not using Themes for this? Themes let you easily toggle from one configuration to another. Is it because of the need to create a Theme for a Core configuration for Figma Variables?

Any Slack thread to link to?

six7 avatar Jul 31 '23 06:07 six7

Here's the slack link: https://tokens-studio.slack.com/archives/C02JAL48UDN/p1688890517400129

keeganedwin avatar Aug 01 '23 07:08 keeganedwin

I do use themes to create Figma Styles, but I don't want to create them for every 'theme'. For instance, I do have component tokens for Light / Dark, but in order not to flood my figma file with styles, I don't create styles for the underlying Light/Dark Semantic tokens.

Now to accomplish this I have to turn off/on the create styles checkbox, which I sometimes forget... So my idea was, what if you could manage that a bit easier, like 'set as source" but in a different way.

vkogmail avatar Aug 01 '23 07:08 vkogmail

Oh got it. So it's more about marking specific sets as hidden from publishing?

six7 avatar Aug 01 '23 08:08 six7

Another used-case:

The problems we have been facing are conflicts between developers and designers. They set up a theme configuration that works well for creating variables in Figma, but it causes issues on the development side. When they adjust it to work properly on the development side, it creates issues on the designer side. They suggest having the ability to create two (or more) distinct theme configurations, allowing them to choose which one will be used by developers and which one will be used for Figma. Like creating:

  • “Dev config” with themes configured for the Devs
  • “Figma mobile config” with themes configured for the mobile designer team
  • “Figma web config” with themes configured for the web designer team

keeganedwin avatar Jan 31 '24 07:01 keeganedwin

@six7 we also can't have the same tokens synced to a repo working in more than one Figma file if they are attached to themes. So if we want to use the same tokens across many files, like when I spin up a new client for my agency, I have to use token sets instead of themes.

SamIam4Hyma avatar Apr 02 '24 15:04 SamIam4Hyma

This request has been moved to our new feedback tool. Go check out https://tokensstudio.featurebase.app/ to create a free account. You can upvote and comment on existing posts, make a new request, and subscribe to be notified when requests move into our roadmap.

LukeFinch avatar Apr 12 '24 16:04 LukeFinch

Added to Featurebase Roadmap : 🌜Theme management (pro) enhancements

UdayHyma avatar Apr 15 '24 09:04 UdayHyma