This much layering and componentization will require a dedicated design system team to maintain and keep it updated as business grows and changes. It is probably more appropriate for a larger organization. For a small design team < 5 people in a startup environment, it may be overly complicated and they probably should use a much simpler structure. A simpler and more straight-forward system will also make onboarding new designers much easier, which happens a lot for startup companies. Designers come and go. The design system should be easy to update for new designers to accommodate new business / brand direction as start up companies find their identities in the ever-changing business environment.
I agree! However, this structure can still be applied in smaller scales. Emphasis is not necessarily on all the different variables required, but on setting it up right so it has the flexibility to grow.
@@UICollectiveDesign Can you please explain me why I need 3 levels of tokens and not 2? I clearly understand 2 - f.e. the storage of all my colors - and then the colors applied to components, so that i can relink idk tabs color, without changing button colors. But why I need one more between them? can you provide me a usecase please
Thank you for the video! Still is unclear what is the purpose of the Alias collection if we can just make from the Purple 500 -> Surface primary. Could you please help me to understand why do we need this additional chain?
I was just going to mention this. Why use an alias level just to add the words primary, secondary, etc. ??? Could we not just call the color on the brand level “purple -primary “
Here's what I've understood: In design system tokenization, the choice between a two-step and three-step process depends on how you structure your tokens. The two-step method (A=B=C) straightforwardly assigns variables, while the three-step approach (A=B; B=C) in the video breaks variables into "what they're used for" (Alias) and "where they're used" (Mapped). The choice of structure-whether to organize by broader to specific categories or by usage contexts-is flexible and depends on your team's preferences and workflow. For instance, you might categorize from a broader category (Alias) to a specific category (Mapped), offering flexibility in how you organize your design system tokens. Both methods achieve the same outcomes, but the primary benefit of using a three-step process over a two-step process in tokenization is to avoid long names and reduce multiple layers of nested groups. This approach can provide greater clarity and organization, especially in large and complex design systems, by breaking down the hierarchy into more manageable parts.
If your alias color collection is the same thing as your brand collection, what's the purpose of creating it? Why not just use the alias naming convention for the brand and use the brand collection to build the mapped collections?
Great question! Your colours need a role. You can also have brand colors, that are not assigned a role. Therefore, brand is not always a 1:1 match of what is in alias.
i watched your other video -> ua-cam.com/video/VoSo2__hN-A/v-deo.htmlsi=gkFqlCBw0kaR9HXR, and there you do this extensively in the variables in figma. but here you have the mapped set, with in that set 'light' , so how would you then add the 'surface colors' part, and the text-color part etc?? i still have the free version of token studio (and free version of figma, because i cant choose between the two and i am not sure which one is worth it. )
Create a profile on our community site so I can invite you to our Slack community. I would be able to better assist you there :) TS offers things that variables does not... such as Github sync, etc... but right now, they are relatively similar. I would suggest starting with variables give the easier learning curve.
Tip for colors: get HSL() and make tokens voor lightness, saturation and hue. And for the tints just drop the lightness. And then for changing the color you only need to change the hue token
sorry, what's the purpose of using Tokens Studio to then just sync to Figma variables? I don't see any advantage in doing that as opposed to just do the setup directly with variables. Am I missing something here?
Which video is this? I was wondering the same. And second question; i am new to tokenstudio and cant find a tutorial how it works ( applying to your design) (free version), do you have a video on that? So i can make a descision which to choose.
Building a color scale just by adding white to create light tones and adding black to create dark tones won't give you rich tints or shades that work well with gradients, and illustrations or that look like what you can find in nature. It is ideal to also make use of the luminance value of color to create a more natural tint or shade.
Rookie indeed! But great to get started. A lot goes into building an accessible pallet and there are so many tools out there that help now.@spikespiegel2511
Setting set to "source" just doesn't work on variables yet (only styles generation), because variables require a full collection setup (core->semantic->component) to keep the aliases.
Hi, I just wanted to say that I'm learning a lot from your videos. This is a bit off-topic, but you have such a beautiful voice, and your pronunciation is so good that I can understand every single word you say, even though English is not my main language! Thanks a lot!
Nope! It's best to avoid component-level tokens where possible. Mapped are not component specific, but if you really need a component level token, it can belong in Mapped.
@@polenunes It can cause overcomplexity and inconsistencies if borders, surfaces, etc... all are unique. Additionally, if a change does need to be made, it must be made across each token, instead of just adjusting one value.
I like 3-tier approach to variable collections, but it looks a bit odd to me to have a very specific variable in the Brand collection - radiusComponent. What's the reason for this? why not have it either in Alias' or Mapped collection?
I really like this structure. But I don't think I would go to the trouble of reorganizing an existing UI kit. I also find it a bit too "bureaucratic" or fragmented. If you could start from scratch, that would be different. Thanks
Filming a video now where I build one from scratch :) Agreed, reorganizing an entire UI kit is aggressive. But for those getting started or have questions about particular tokens, this was meant to help.
on 16:50 where you make color scale there a much easier way to do this. When you select a color just change HEX to HSB and change the two fields in the middle that represent white and black.
Everybody uses the color scale method in their design system. It looks good in the docs but who actually uses all the variants of those colors. You may for a hover, maybe a pressed state but the others I can never find a use for. Love the video. Not trying to detract from it. Just something see a lot. Would love to hear how other make use of the spectrums of color from their DS.
So true. I like to keep my color scales to 5 or 6 to keep things clean. In one of my recent videos where we build out a library, I touch on this. Agreed that a ton of colors look nice in docs, but 80% of them just sit there.
I was watching some more of your vids this morning, and I came across this mention. Great content. Question, I noticed while running through some quick tests that in some cases, even though i'm on Figma enterprise I would get a popup saying I needed to pay $75 per seat to use variables. Do you know what the rule is, how many variables you can leverage before you're cut off?@@UICollectiveDesign
@@UICollectiveDesign For shades of grey I need many of them and when it comes to colored labels (e.g. unsaturated color as background, saturated for text) that each have a hover state and a pressed state you quickly need much too from my experience.
It really comes into play when you get into themes. We have an app that gives the options of Light, Dark, and High Contrast modes. Having a full spectrum of each color to work with makes things much easier.
I have one question, if we are using color theme as purple 500, 600, 800 etc and my primary brand color is 800. If future if the brand color got changed and new brand color is green 500, then how would it work across for changing colors?
@@UICollectiveDesign in approach one this will still work but in approach 2 it is going to impact. Imagine in the current hover I used primary 400, and post new brand color update my primary will be 800, but over will be still 400 in whatever color shade it is available.
So my question was something similar to this. Let’s say as example you got on the basic token level of colors. Something like green , scaling from 1-9 lightest to darkest. Obviously 5 is the primary. Anyways. So all is connected to the level of mapping. But now the company has decided that the brand color is going to change to a blue. So, how do u link this in tokens without breaking it all. I mean is easier for designers to just go to tokens and change the variable name to BLUE and change the values, but what about on dev side. Cuz they need a consistent name for the tokens they use. Meaning they will have to change all their names now from green to blue. Not sure if there is a better name convention to use at the first level rather than just the color name.
@@vaibhavnaik12 Yeah there would be some manual work there to repoint tokens, but no need to adjust anything in your brand collection... you're essentially just selecting a different primary color. Request to join our Slack and I can help you troubleshoot/
What would be your approach if a black #00000 is needed and/or white? Would you include them in a grey scale brand color or separate as the grey? How do you name it in the alias when a black can be primary text and secondary surface at the same time? thanks for your content! :)
Thank you! That was very helpful. I got the problem, that my tokens studio tokens and the figma variables and styles tending to lose connection between each other. besides the fact that naming and grouping are the same. is there a way to tie them up in a way that they are always synced in real time? I remember that this was once possible but can't remember how.
Thanks for the video, it's helping me a lot! I have a question: when you synchronize tokens to variables, what happens to my typography tokens? Does it convert them as well or do they become styles?
This much layering and componentization will require a dedicated design system team to maintain and keep it updated as business grows and changes. It is probably more appropriate for a larger organization. For a small design team < 5 people in a startup environment, it may be overly complicated and they probably should use a much simpler structure. A simpler and more straight-forward system will also make onboarding new designers much easier, which happens a lot for startup companies. Designers come and go. The design system should be easy to update for new designers to accommodate new business / brand direction as start up companies find their identities in the ever-changing business environment.
I agree! However, this structure can still be applied in smaller scales. Emphasis is not necessarily on all the different variables required, but on setting it up right so it has the flexibility to grow.
@@UICollectiveDesign Can you please explain me why I need 3 levels of tokens and not 2? I clearly understand 2 - f.e. the storage of all my colors - and then the colors applied to components, so that i can relink idk tabs color, without changing button colors. But why I need one more between them? can you provide me a usecase please
Thank you for the video! Still is unclear what is the purpose of the Alias collection if we can just make from the Purple 500 -> Surface primary. Could you please help me to understand why do we need this additional chain?
I'd like more clarity on this also
I was just going to mention this. Why use an alias level just to add the words primary, secondary, etc. ??? Could we not just call the color on the brand level “purple -primary “
@@1deplatt what if client or you decide that purple is not primary anymore?
Here's what I've understood: In design system tokenization, the choice between a two-step and three-step process depends on how you structure your tokens. The two-step method (A=B=C) straightforwardly assigns variables, while the three-step approach (A=B; B=C) in the video breaks variables into "what they're used for" (Alias) and "where they're used" (Mapped).
The choice of structure-whether to organize by broader to specific categories or by usage contexts-is flexible and depends on your team's preferences and workflow. For instance, you might categorize from a broader category (Alias) to a specific category (Mapped), offering flexibility in how you organize your design system tokens.
Both methods achieve the same outcomes, but the primary benefit of using a three-step process over a two-step process in tokenization is to avoid long names and reduce multiple layers of nested groups. This approach can provide greater clarity and organization, especially in large and complex design systems, by breaking down the hierarchy into more manageable parts.
Nailed it!!
If your alias color collection is the same thing as your brand collection, what's the purpose of creating it? Why not just use the alias naming convention for the brand and use the brand collection to build the mapped collections?
Great question! Your colours need a role. You can also have brand colors, that are not assigned a role.
Therefore, brand is not always a 1:1 match of what is in alias.
@@UICollectiveDesign Great..
@@Akram-UXUI Glad it helped!
@@UICollectiveDesign Cant they then be added as styles rather than adding in brand collection variable?
@@cintiapena1696 They can as well, but the variables are wrapped inside of the styles :)
i watched your other video -> ua-cam.com/video/VoSo2__hN-A/v-deo.htmlsi=gkFqlCBw0kaR9HXR, and there you do this extensively in the variables in figma. but here you have the mapped set, with in that set 'light' , so how would you then add the 'surface colors' part, and the text-color part etc?? i still have the free version of token studio (and free version of figma, because i cant choose between the two and i am not sure which one is worth it. )
Create a profile on our community site so I can invite you to our Slack community. I would be able to better assist you there :)
TS offers things that variables does not... such as Github sync, etc... but right now, they are relatively similar. I would suggest starting with variables give the easier learning curve.
Tip for colors: get HSL() and make tokens voor lightness, saturation and hue. And for the tints just drop the lightness. And then for changing the color you only need to change the hue token
Great call out!!
sorry, what's the purpose of using Tokens Studio to then just sync to Figma variables? I don't see any advantage in doing that as opposed to just do the setup directly with variables. Am I missing something here?
With Figma's variable release in December, there isn't much point anymore. Will be releasing a video next week on this....
@@UICollectiveDesign gotcha, thanks for the answer. I'll be looking forward for the new video
@@problemimentali me too
Just posted the vid this morning@@problemimentali
Which video is this? I was wondering the same.
And second question; i am new to tokenstudio and cant find a tutorial how it works ( applying to your design) (free version), do you have a video on that? So i can make a descision which to choose.
Building a color scale just by adding white to create light tones and adding black to create dark tones won't give you rich tints or shades that work well with gradients, and illustrations or that look like what you can find in nature. It is ideal to also make use of the luminance value of color to create a more natural tint or shade.
Agreed - This is just an example :) I appreciate the dialogue!
Rookie indeed! But great to get started. A lot goes into building an accessible pallet and there are so many tools out there that help now.@spikespiegel2511
the better approach is uniform color using oklch() or learning munsell color system
I think font size token is missing
Sorry this must have been a recording oversight
Setting set to "source" just doesn't work on variables yet (only styles generation), because variables require a full collection setup (core->semantic->component) to keep the aliases.
Great call out :)
Thank you for these videos! Super helpful as I transition from component-based to semantic tokenization
Happy to help! Please subscribe and share our channel/vids where you can :)
Hi, I just wanted to say that I'm learning a lot from your videos. This is a bit off-topic, but you have such a beautiful voice, and your pronunciation is so good that I can understand every single word you say, even though English is not my main language! Thanks a lot!
Really appreciate the kind words!!! Please subscribe and share our channel on social media where you can :) Your support goes a long way!
So your mapped collection is same as component tokens?
Nope! It's best to avoid component-level tokens where possible. Mapped are not component specific, but if you really need a component level token, it can belong in Mapped.
@@UICollectiveDesign Why it is best to avoid component level tokens?
@@polenunes It can cause overcomplexity and inconsistencies if borders, surfaces, etc... all are unique. Additionally, if a change does need to be made, it must be made across each token, instead of just adjusting one value.
Hi again! Your teaching style is so clear and easy, I've understood the concept very well. Thanks 🤩
Happy to hear that! Please subscribe and share our channel where you can :)
So if the brand colors given from the brand team are already aliases like "CTA Blue" and "Primary Blue", what would your approach be?
Primary/Blue is fine. CTA Blue would become Surface/Primary
If you do a super simple design system how would you simplify all these colors, sizes, etc?
That depends on the use-case. This already is quite simple as is.
can we make some new color that has some opacity with it, but we use the reference form the brand/global tokens?
Absolutely!!
I like 3-tier approach to variable collections, but it looks a bit odd to me to have a very specific variable in the Brand collection - radiusComponent. What's the reason for this? why not have it either in Alias' or Mapped collection?
Great question, I would watch the following video ua-cam.com/video/WATzIK0Ai8I/v-deo.html
@@UICollectiveDesign This link takes to this same video :)
I really like this structure. But I don't think I would go to the trouble of reorganizing an existing UI kit. I also find it a bit too "bureaucratic" or fragmented. If you could start from scratch, that would be different. Thanks
Filming a video now where I build one from scratch :)
Agreed, reorganizing an entire UI kit is aggressive. But for those getting started or have questions about particular tokens, this was meant to help.
@@UICollectiveDesign Sure ❤️
I have learnt a lot from your videos. keep going brother.
A lot more on the way! Please subscribe and share our channel where you can :)
on 16:50 where you make color scale there a much easier way to do this. When you select a color just change HEX to HSB and change the two fields in the middle that represent white and black.
Great call out!
@@UICollectiveDesign Do you mean modify Saturation and Brightness?
Reducing the Saturation by 50%, is the same hex as taking your primary, reducing opacity by 50%, color matching with the extra square workflow.
That works as well!@@bradmacdonald6591
Everybody uses the color scale method in their design system. It looks good in the docs but who actually uses all the variants of those colors. You may for a hover, maybe a pressed state but the others I can never find a use for. Love the video. Not trying to detract from it. Just something see a lot. Would love to hear how other make use of the spectrums of color from their DS.
So true. I like to keep my color scales to 5 or 6 to keep things clean. In one of my recent videos where we build out a library, I touch on this.
Agreed that a ton of colors look nice in docs, but 80% of them just sit there.
I was watching some more of your vids this morning, and I came across this mention. Great content.
Question, I noticed while running through some quick tests that in some cases, even though i'm on Figma enterprise I would get a popup saying I needed to pay $75 per seat to use variables. Do you know what the rule is, how many variables you can leverage before you're cut off?@@UICollectiveDesign
@@UICollectiveDesign For shades of grey I need many of them and when it comes to colored labels (e.g. unsaturated color as background, saturated for text) that each have a hover state and a pressed state you quickly need much too from my experience.
It really comes into play when you get into themes. We have an app that gives the options of Light, Dark, and High Contrast modes. Having a full spectrum of each color to work with makes things much easier.
I have one question, if we are using color theme as purple 500, 600, 800 etc and my primary brand color is 800. If future if the brand color got changed and new brand color is green 500, then how would it work across for changing colors?
Can you can adjust the brand primary in Alias
@@UICollectiveDesign in approach one this will still work but in approach 2 it is going to impact. Imagine in the current hover I used primary 400, and post new brand color update my primary will be 800, but over will be still 400 in whatever color shade it is available.
So my question was something similar to this. Let’s say as example you got on the basic token level of colors. Something like green , scaling from 1-9 lightest to darkest. Obviously 5 is the primary. Anyways. So all is connected to the level of mapping. But now the company has decided that the brand color is going to change to a blue. So, how do u link this in tokens without breaking it all. I mean is easier for designers to just go to tokens and change the variable name to BLUE and change the values, but what about on dev side. Cuz they need a consistent name for the tokens they use. Meaning they will have to change all their names now from green to blue. Not sure if there is a better name convention to use at the first level rather than just the color name.
@@whennn This is where you just adjust your primary color. No need to adjust the names in the brand collection
@@vaibhavnaik12 Yeah there would be some manual work there to repoint tokens, but no need to adjust anything in your brand collection... you're essentially just selecting a different primary color. Request to join our Slack and I can help you troubleshoot/
Thanks for your amazing content.
Glad you like it :) Please subscribe and share our channel
Thank you, I love this tutorial
Glad it helped!
What would be your approach if a black #00000 is needed and/or white?
Would you include them in a grey scale brand color or separate as the grey?
How do you name it in the alias when a black can be primary text and secondary surface at the same time?
thanks for your content! :)
I would watch this video I released two weeks ago :) : ua-cam.com/video/VoSo2__hN-A/v-deo.html
Thank you for popularizing these concepts, this video is a pleasure to watch! 🙂
Glad you like it! Please share the video :)
Thank you! That was very helpful. I got the problem, that my tokens studio tokens and the figma variables and styles tending to lose connection between each other. besides the fact that naming and grouping are the same. is there a way to tie them up in a way that they are always synced in real time? I remember that this was once possible but can't remember how.
Don't believe they can be synced in real-time. I am sure there is a plugin for this though
Have you found a solution meanwhile?
@@Fabian-fk8qs yes. When creating a theme you have to sync styles and variables in the theme. That writes a json with the respective styles id
@@nutellanorbert2799 Thank you very much! :)
Thanks for the video, it's helping me a lot! I have a question: when you synchronize tokens to variables, what happens to my typography tokens? Does it convert them as well or do they become styles?
Depends if you choose to sync to variables or create the styles :)
& glad the video helps! Please subscribe and share the vid where possible. All support helps!