Back to the Future of Hypermedia in Django
summary
Django leads hypermedia adoption in Python and the concrete claim is that using HTMX with Django lets servers send only partial HTML fragments using HTMX headers (HX-Request) and template fragment tools like django-htmx, django-render-block, django-template-partials. A real SaaS migration replaces a React front end with HTMX in two months with no UI compromise and measurable wins: 21,500 → 7,000 lines of code, JavaScript deps 255 → 9, build time 440s → 5s, and roughly half the time to interactive.
AI-written summary · about
chapters (11)
- 0:00Hypermedia origins
- 3:21REST and HATEOAS
- 5:10Hypermedia for CRUD
- 8:19HTMX and Django
- 10:28Django-HTMX patterns
- 13:45Partial content with HTMX
- 16:37HTMX tools in Django
- 18:24HTMX production readiness
- 20:13Python and hypermedia
- 21:55HTMX with Tailwind
- 22:59Conclusion
related talks
26mModern web apps with (almost) no JS: Enhancing UX with HTMX in Django
35mJavascript Fatigue: Back to Hypermedia w/ Django+HTMX
37mHTMX: Frontend Revolution
26mReimagining dynamic web apps with HTMX
30mHTMX vs WASM - more backend or more frontend?
30mBest buddies: Django and HTMX
26mUsing Django 4.2's StreamingHttpResponse and HTMX SSE to provide real time notifications
46mDjango + Alpine.js + htmx Ups & Downs with Karen Tracey