HTML, CSS and the Clientside App
summary
Argues that HTML5 and CSS are active parts of client-side apps, not mere presentation: use native features like contenteditable inline editing and built-in form types/validation to eliminate DOM wiring, let the browser store current state (dot coordinates updated natively and posted with a small save function), prefer one template partial per widget and a renderer that caches compiled templates, separate CSS and JS hooks so each has its own class, and lazy-load CSS per widget and one plugin per widget to reduce JavaScript surface.
AI-written summary · about
chapters (11)
- 0:00HTML and CSS basics
- 4:01Why HTML/CSS matter
- 10:16HTML/CSS mistakes
- 15:13Over-nesting pitfalls
- 21:16HTML as typed data
- 29:19Choosing templating engine
- 35:11Reusable templates
- 41:09Views as components
- 44:19CSS for state/workflow
- 48:13Lean on HTML/CSS
- 49:53Q&A
related talks
36mStop using JS for that: moving features from JS to CSS & HTML
33mThe Purification of Web Development
30mStop using JS for that: Moving features to CSS and HTML
29mCSS Architecture for Modern Web Applications
57mDo It With Style: Rethinking CSS
45mCSS-in-JS: FTW
20mTo hell with jQuery
32mBetter Production Decisions with HTML & CSS