Yak-shaving to Where the Puck is Going to Be.
summary
Shows two working third‑party projects: Neapolitan — a single-file CRUD class that instantly wires list/detail/create/edit/delete for a model, ships base templates and tags, depends on django-filter, and reads top-to-bottom in the time it takes to drink a coffee; and template partials — an inline partial system plus a template-loader hack so views can return "template#partial" unchanged. Both target HTMX workflows (HTMX + Alpine + Tailwind), already usable and evolving, not core yet.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:37Yak shaving context
- 3:17Locality of behavior
- 6:43Django class-based views
- 9:40Vanilla views concept
- 11:25Introducing Neapolitan
- 15:24Django template partials
- 18:47Core vs third-party
- 20:43Q&A session
related talks
46mDjango + Alpine.js + htmx Ups & Downs with Karen Tracey
26mModern web apps with (almost) no JS: Enhancing UX with HTMX in Django
18mBuilding theatlantic.com homepage’s WYSIWYG admin with...
26mAPI Maybe: Bootstrapping a Web Application circa 2024 with Carlton Gibson
53mDjango: a Data Shovel With a Future
43mChoosing Wisely: SPA vs. HTMX for Your Next Web Project with Chris May
54mAdvanced Aspects of the Django Ecosystem: Haystack, Celery & Fabric
23mVue + Django: Combining Django Templates and Vue Single File Components without compromise