A red LEGO brick is always red components on the web
summary
Explains concrete patterns: one-folder-per-component, treat components as black boxes, pull business logic out and keep components presentation-only; use React and register-as-web-elements via reactive elements to inject components into a Django server-rendered site; compare CSS strategies — CSS modules vs style component — and use a webpack build to hash class names; measure complexity by lines of code and HTML nodes, allow explicit component variants, and cites roughly 50 components deployed at Threads.
AI-written summary · about
chapters (8)
- 0:00Start
- 4:31MVC doesn't fit frontend development
- 7:53Approaches and challenges of building good components
- 11:35Reusable components have to be configurable
- 22:34Beware breaking the abstraction
- 23:37Giving components data.
- 25:04The path to components today
- 28:36The "black boxyness" of components lets you try new technology
related talks
05mReact is the new Lego - how we deal with a lot of components
41mBuilding Your Legos: A Practitioner’s Guide to Reusable Components
25mReact Bricks: a CMS with visual editing based on React components
28mFront End Legos: Better Design with Reusable HTML & CSS
42mComponents everywhere! - Bridging the gap between backend and frontend
28mReact Inline Visual Editing Now’s The Time
42mReact, Another Way to Think About Your Web Components
25mSimply React