The Purification of Web Development
summary
Argues for component-driven CSS: a predictable class scheme (eg SUIT CSS), packaged components via bower packages, and native encapsulation with shadow DOM and custom elements. Gives concrete workflow: isolated button component in a repo, reused across tweetdeck and twitter com so the button hasn’t been rewritten for a year. Describes scale: hundreds of components maintained by dozens of developers, explains testing with simple HTML/CSS fixtures and how web components prevent style leakage.
AI-written summary · about
chapters (6)
- 0:00Start
- 8:23The History of Html and Css
- 15:06Ugly Class Names
- 25:58Promise of Web Components
- 27:05Shadow Dom
- 29:01Clarity of Renaissance
related talks
56mModern CSS For Dynamic Component-Based Architecture
28mAdaptation and Components
17mThinking beyond “Scalable CSS”
40mThe ABC's of Architecting Better CSS
32mYou've been doing CSS wrong
16mCSS, Design Systems & Developer Experience
01h 11mUtility-first CSS: The highs and lows of styling web sites
45mCSS-in-JS: FTW