Unpoly - Single Page Experience with Server-Side Rendering
summary
Unpoly delivers server‑side rendered pages with SPA behavior by swapping fragments via HTML attributes and a single JS file, demonstrated with Jakarta MVC, JTE templates and Pico CSS; the demo app deploys without full-page reloads, charts use a cached-first fetch with a 5s backend delay and a 15s default cache, forms return 400/422 for validation and redraw appropriate fragments, layered modal interactions preserve form state, integration uses compilers for third‑party widgets like lit-line, all implemented with ~100 lines of JavaScript and a 50KB single JS file.
AI-written summary · about
chapters (9)
- 0:00Introduction to Unpoly
- 3:37How Unpoly works
- 6:08Demo setup and basics
- 8:37Partial updates and attributes
- 12:31Caching and history
- 14:46Form handling
- 20:52Sub-interactions
- 25:15Third-party JS integration
- 29:33Summary and closing
related talks
32mUnpoly to Take Back Control!
55mTechnology agnostic microservices at SPA frontend
29mProject Hummingbird
51mBuilding Amazing Single Page Applications the Right Way
41mRapid server side full stack web development with ViewComponents and htmx
32mWhy you don’t need a Single Page App
43mRefactoring to a Single Page Application
47mCamel and Eye of a Needle: Integration Approaches for SPA-based Micro Frontends