Joey Banks explains why new features are so important for the design systems’ work.

Sho Kuwamoto, Director of Product at Figma, on new features and applying the concept of ​“composition” from engineering to design systems.

New component property features in open beta: exposed nested instances for more customization, preferred values for more clarity when instance swapping, and simplified instances for more focus on relevant properties.

Luis on why it’s important to optimize for the usage of components.

A quick look at the process of updating an existing component with Component Properties and releasing an update with minimal friction for the design team.

Molly Hellmuth shares a few things she learned about using Component Properties after rebuilding a design system from scratch.

Generate all possible instances for your components, including every combination of variants and component properties, all in a tidy labeled table.

“In this stream, Figma Designer Advocate Chad Bergman and Product Manager Jacob Miller share how to apply polish to your components and publishing a v1 of your library.”

Rogie comes to the rescue and explains how to preserve a fill color when icons are overridden and swapped. It’s worth keeping a layer name consistent across icons in the library if you plan to use them in different colors.

That’s a really smart idea — browse a library of pre-made UI elements and copy-paste them straight to Figma. Categories make browsing the collections very easy. May be valuable for rapid prototyping at the early stages or for exploring ideas. (Keep in mind it didn’t work for me in Safari, but works perfectly in Chrome.)

Ridd shares five awesome strategies for using component properties: strategic nesting, progressive disclosure, minimizing decisions, emojis, and streamlining the instance swap.

Edward Chechique wrote a detailed and well-illustrated guide to component properties.

Figma dropped a new tutorial: ​“With component properties, you can define which parts of a component can change. And instead of creating separate variants, you can use component properties to reduce the number of components needed. This takes the guesswork out of designing for anyone using these components and they can quickly make adjustments as Figma keeps component property controls in one place.”

“We’re excited to talk about yet another awesome new feature: Component properties. Join us as product manager Jacob Miller and designer advocate Chad Bergman share more on how you can reduce variant explosion in your design systems and improve developer handoff.”

Ridd warns that using component properties introduces a new type of responsibility for designers and explores what the most effective handoff deliverable actually looks like.

Luis shows a neat trick on how to create an ​“infinite table” using component properties, where we can toggle on however many columns or rows we need in designs.

Follow Charli Marie’s live stream of working on a quote component and figuring out how to use Component Properties.

Molly Hellmuth with 5 step-by-step examples on how and when to use Component Properties.

Vic, a systems designer working on design systems at Microsoft, wrote a case study on Component Properties with practical examples, some interesting issues and workarounds, and thoughts on why they might be moving away from base components.

Joey Banks on component properties: ​“In the past few weeks, I’ve had the chance to become more comfortable creating components that contain component properties. What has helped me the most has been to think of this new feature as an additional way, not a separate way, to further organize and create components and variants that scale with the library and system.”