Office hours: Variables migration best practices 

I appreciate you mentioning my Styles to Variables Converter plugin. While it's intentionally kept basic (it has no UI), it’s great you also highlighted Yann's plugin, which offers more robust features, including mode creation. Good to be part of the Figma community! 😊

Clear and concise. thanks!

Ooo this is nice! Thanks :)

Good overview. Thanks. I was however disappointed that no mention was made about image variables.

It would be so helpful to get Expressions (made with multiple variables), for example to maintain an aspect ratio we could have: height = width*1,33 (this the TV frame 4:3). So we when we resize our design screen, the aspect ratio adapts.

Super helpful video, thank you! Im wondering, doesn't it defeat the purpose of naming the sizing primitives by putting the value in the name? Would it make more sense to name the primitives something that isn't the value in case you want to change one of the sizing primitives value in the future?

To export/import variables between projects is necessary. I've tried a couple of plugins but as with all plugins they are unstable and not very well maintained, also they lack the ability to keep connections between the tokens when the JSON files are imported, so it's kinda messy. Should be easy to just pick a variable setup from wherever you are in Figma and start using them.

Hello, thanks for this video. Great resource! I tried your suggestion, putting primitives in a separate files and aliases in another in order to hide primitives. Then I used the aliases file in a test file referring just to the alias file. Variables from the primitives file are not shown and offered anymore, which is fine. However the mode from the primitives file is still available for selection, which increases the amount of modes offered ... 😞 primitives aliases

Is possible to apply variables for opacity and border width?

Is there a way to organize the list of the Collections? Wish it didnt force me to have it on a alphabetical order. Maybe even have small titles to separate the list a little bit more

What font is that handwritten font from this presentation? I really like it.

Where can I find the Swatchy link? Is it a plugin for Figma?

is there a way to export a CSV of variables? I have 2 files, one for light mode and other for dark mode, I would love to convert the styles to variables, export a CSV, combine them and then import the variables with the plugin sheets to variables, but i can't find a way to export them :(

can someone explain me more, why we should create primitive instead of just straight forward create semantic only?

Why can't the primitive colors be the styles most of us already have established?

l feel like this is a great tool for designers, but sometimes we spend too much time trying to figure out things like this when it would actually be better if instead we learned how it translates to code. At the end, Figma is just a design tool, and all of these over compliated features might take up too much space of the learning of designers when in reality it would be more benefitial and efficient if they focused on other things. Figma might be the tool of the design process, but l feel like sometimes we forget that there is the developement part afterwards. I don't know if l made my point clear but l feel like this is a discussion that l've been seeing more and more. My question is, who really benefits from features like that?

Now waiting for typography variables

I want to get out from Token Studio to Variables completely. Cannot wait for that future

cool... so i guess making more and more and more steps and using more and more plugins is the future..... ugh what a headache

My brain isn't cooperating with this :/

I enjoy the Figma tutorial series, but I've noticed that they're becoming quite lengthy. I hope they can create shorter video series. Additionally, I would appreciate more demos and examples rather than just talking in a presentation style, as it can be challenging to stay focused for an extended period.