But that means it’s now up to us to discover better ways of communicating all the potential forms our components can take.
Maybe that looks like assembling decks of example instances, explaining how the different component properties interact with each other, or explicitly defining ways components shouldn’t be used.
On one hand, component properties make our lives easier…
But on the other, they do add a bit of new work to our plate. Because now it’s our responsibility to guide designers/engineers to ensure our components are being used correctly.
As a whole, this all feels like a massive step in the right direction though. And I’m really excited to see how it pushes designers to communicate more effectively moving forward.
3 — Exposing nested components at the parent level is a BIG deal
If you’ve been following me for a while or enrolled in Figma Academy, you know that I am a huge fan of nested components and all that they unlock.
Up until Config, the only valid reason for avoiding them was that they weren’t intuitive because you couldn’t immediately see which nested instances lived inside of the main component. Well not anymore…
Now we can add an instance swap at the parent level. That means when someone clicks on a component they can immediately see which subcomponents are interchangeable.
This unlocks the full potential of atomic design.
But by far my favorite application is how it affects “Slot” components 👇