Architecting Subcomponents

Architecting Subcomponents - Nathan Curtis

Рет қаралды 13,593

Жыл бұрын

Playing constant catch up, adding prop after prop to support and maintain too many cases? Break larger components into flexible subcomponents so that users can solve their unique problems themselves. We'll show how to architect subcomponents, leverage Figma's improving component features, embrace opportunities and challenges the approach creates for your system.
Schema by Figma is a conference focused on design systems. For more info, check out designsystems.com/sections/schema
Figma is free to use. Sign up here: bit.ly/3msp0OV
____________________________________________________
Find us on ⬇️
Twitter: / figma
Instagram: / figma
LinkedIn: / figma
____________________________________________________
#Figma #Schema #FigJam #Tutorial #NothingGreatIsMadeAlone #design #tips #schema2022 #DesignSystems

Пікірлер: 16

@danielDefoe81 Жыл бұрын

God damn, 20 Minutes is way to short for Nathan. You guys should invite him to some office hours events

@jswanson859 Жыл бұрын

Love this one! So much great Information to take back to my team.

@martacondedesigner Жыл бұрын

This is gold 😍!! Thanks to share ^^

@hoangocnguyen6368 Жыл бұрын

awesome!!!

@senithbgajanayake1754 Жыл бұрын

Super!

@irfanadamm5819 Жыл бұрын

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 Жыл бұрын

Can you explain deeper what you mean?

@irfanadamm5819 Жыл бұрын

@@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.

@FranEnchufes Жыл бұрын

@@irfanadamm5819 Thanks a lot for taking the time to expand your explanation

@rajeshsatyarthi Жыл бұрын

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.

@SM80FG Жыл бұрын

FAIRFAX WOO WOO!

@grafin29 Жыл бұрын

Subcomponents is available now?

@platinumdynamite Жыл бұрын

You've been able to do this for a long time - it's simply nesting components within each other for better modularity.

@grafin29 Жыл бұрын

Idea with slots is great. But How I can reorder subcomponents inside main component, now?

@platinumdynamite Жыл бұрын

@@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.