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

Miggi shows how to make a reusable and flexible tooltip component set using Auto Layout, absolute positioning, constraints, and component properties.

Miggi plays with component properties, Auto Layout slots method, and Interactive Components to make some fun modular content prototypes.

To answer some common questions about Component Properties, Tom Lowry re-recorded the little run-through that he did during one of the breaks at Config.

Ridd is rethinking his approach to content systems with the introduction of Component Properties.

Joey Banks creates a button component using both Variant Properties and Component Properties.

Nathan Curtis wrote a really detailed 3‑part series on building a workflow to assure the quality of design system assets.

Ridd shows why the new Instance Swap component property ​“blows the roof off of what we can do with components”.

Great improvement that wasn’t highlighted during the keynote.

Andrey Okonetchnikov makes a case for thinking twice before introducing a boolean property when modeling an API of the component as it can hide complexity and introduce impossible states.

Speaking of base components, Greg Huntoon explains why he decided to stop using them and how he used Automator plugin to decouple base components from the design system.

Ridd discusses a few key principles for using base components: How often are you iterating on the component? How complex is it? Avoiding problems with Interactive Components. Pairing primitives with slots. Bringing in base components early on to speed up the process.

Joey Banks shares how he typically names Variants in Figma and the approach he tries to take whenever he is feeling stuck.

“How can we update and test our design system components in Figma? With branching, we have a space to explore updates in our main library files while keeping the source of truth intact. And, with Swap Library, we can quickly change what libraries are being used in a file. Let’s take a look at how we can use these features together to iterate and test our components.”

Anton Kuznetsov wrote a detailed guide to creating components with customizable content, better known as ​“slot components”. This approach is the best way to reduce the number of detached instances in your project.

Hosts of the Design Details podcast share tips for crafting component variants to avoid the dreaded variant-explosion problem.