The Revenge of Static Builders
summary
Argues that mixing frameworks per component and serving most markup prebuilt cuts client JS by moving interactivity to partial hydration and the islands architecture. Demonstrates tools: Astro (site built with it), Slinkity/11ty plugins, MDX/MDGS for embedding components, and bundlers like Vite and Snowpack. Recommends Svelte for <3 instances, Solid for 3–10, Preact beyond 10, and shows design systems + web components let teams ship isolated, tested islands that hydrate on viewport or idle scheduling.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:46Static builders matter
- 3:52Traditional SSG limits
- 9:13Component dehydration
- 12:48Partial hydration
- 15:58Islands architecture
- 17:42Modern tooling
- 19:48Frameworks with design systems
- 22:37Components in markdown
- 25:27Astro Iliad Slinkity
- 27:19Astro features
- 30:50Choosing frameworks
- 33:19Extending Astro
- 34:46Static builders future
- 35:27Q&A
related talks
31mFaster content websites via SSR and progressive hydration of Web Components
45mGive Me Back My Frontend!
27mYou might not need a meta framework
31mBack to boring
28mLa nouvelle vague
24mThe Good, The Bad, and The Web Components
50mComposable decoupled frontends: the Jamstack and beyond
13mReact Without JavaScript?