Architecting Subcomponents - Nathan Curtis

Подписаться 538 тыс.

Просмотров 13 тыс.

50% 1

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

Наука

Опубликовано:

18 ноя 2022

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 16

@danielschultheiss81 Год назад

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!!!

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

@senithbgajanayake1754 Год назад

Super!

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