Architecting Subcomponents
summary
Argues that instead of inflating a card component with endless props or forcing users to rebuild from scratch, break it into smaller parts so adopters can compose in minutes rather than wait months for feature requests; demonstrates three subcomponent patterns (lockup, extension, alternatives) and four container types (slot, substitution, block, zone) implemented in Figma, shows that nested instances and dropping assets work for real, and notes tradeoffs: better precision and speed but more docs, governance, and learnability.
AI-written summary · about
chapters (10)
- 0:00Architecting subcomponents
- 1:54Designers need subcomponents
- 5:25Subcomponent patterns for cards
- 7:33Container types for subcomponents
- 12:07Choosing subcomponent patterns
- 13:54Material UI component anatomy
- 15:19Subcomponents empower users
- 16:41Approaches to building components
- 19:29Adopting subcomponents challenges
- 21:12Control versus user freedom








