Fear of detaching and redoing, should be the prime motivator to use tokens and substructures. Move level of abstraction to primitives or sources of truths.
@@FranEnchufes in a nutshell. All basic design decisions should function in a master location, like a knob. So that designers are only putting together the final output. Without worrying about consistency. Of course deviations can be accommodated from the corresponding updates in the system. Look at it from the theming point of view. You shud just be able to swap tokens and the whole app is changed. This requires all nodes in the design framework to remain unbroken.
yeah, but figma doesn't have a full support for Design Toekns yet, we do have Token Studio (formerly Figma Tokens) but you can not use tokens inside figma as an alternative to props. Infact W3C still working on Design Token Standards that will officially bring solution to Naming Conventions, Character Litmits, Nesting, and Architecture.
@@grafin29 Forget the idea of 'subcomponents', and just know that the parts within a component can also be instances of another component. You can put a form field and a button together and that can be a component. That's essentially the idea. Unless you're building a complex design library, I'd be careful not to over-employ this, because it creates a very specific system of dependencies that need to be equally maintained or you'll break multiple levels of components.
God damn, 20 Minutes is way to short for Nathan. You guys should invite him to some office hours events
Love this one! So much great Information to take back to my team.
This is gold 😍!! Thanks to share ^^
awesome!!!
Super!
Fear of detaching and redoing, should be the prime motivator to use tokens and substructures. Move level of abstraction to primitives or sources of truths.
Can you explain deeper what you mean?
@@FranEnchufes in a nutshell. All basic design decisions should function in a master location, like a knob. So that designers are only putting together the final output. Without worrying about consistency. Of course deviations can be accommodated from the corresponding updates in the system.
Look at it from the theming point of view. You shud just be able to swap tokens and the whole app is changed. This requires all nodes in the design framework to remain unbroken.
@@irfanadamm5819 Thanks a lot for taking the time to expand your explanation
yeah, but figma doesn't have a full support for Design Toekns yet, we do have Token Studio (formerly Figma Tokens) but you can not use tokens inside figma as an alternative to props. Infact W3C still working on Design Token Standards that will officially bring solution to Naming Conventions, Character Litmits, Nesting, and Architecture.
FAIRFAX WOO WOO!
Subcomponents is available now?
You've been able to do this for a long time - it's simply nesting components within each other for better modularity.
Idea with slots is great. But How I can reorder subcomponents inside main component, now?
@@grafin29 Forget the idea of 'subcomponents', and just know that the parts within a component can also be instances of another component. You can put a form field and a button together and that can be a component. That's essentially the idea.
Unless you're building a complex design library, I'd be careful not to over-employ this, because it creates a very specific system of dependencies that need to be equally maintained or you'll break multiple levels of components.