Django + Alpine.js + htmx Ups & Downs with Karen Tracey
summary
Uses Django with htmx and Alpine.js on several real projects including one Greenfield project that ships a multi‑step form flow; claims server-rendered HTML plus light frontend state keeps validation and routing in Django and reduces duplication. Wins: faster feature delivery, more cross‑training, reuse of Django forms. Downsides: templates become crowded with Tailwind classes and htmx/Alpine attributes, templated JavaScript and component reuse get brittle. Overall verdict: winning combination worth continuing with tighter template/component guidelines.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:23Promise of Django, HTMX, Alpine.js
- 9:22HTMX and Alpine.js together
- 15:02Real-world project experiences
- 18:38Challenges and downsides
- 25:22Overall assessment and future
- 28:56Q&A
related talks
26mModern web apps with (almost) no JS: Enhancing UX with HTMX in Django
35mJavascript Fatigue: Back to Hypermedia w/ Django+HTMX
30mBest buddies: Django and HTMX
24mBack to the Future of Hypermedia in Django
37mHTMX: Frontend Revolution
18mBuilding theatlantic.com homepage’s WYSIWYG admin with...
41mRapid server side full stack web development with ViewComponents and htmx
26mReimagining dynamic web apps with HTMX