~/talk

Taming Your Templates: Component-Based Frontends in Django

Talkat DjangoCon US 2026 · 2026-08-24..08-28· [frontend-architecture, django]
slides:none on file

Argues that Django templates can be component-first without a heavy JS build pipeline, with concrete tooling and tradeoffs: django-includecontents adds props, slots and Jinja support so templates read like components and allow incremental adoption; alternatives include django-cotton, Slippers, Django View Component, Wagtail PyPI for per-page bundling, and HTMX/Alpine for selective interactivity. Notes performance: fastest templates are the flattest (many includes hurt server time and caching matters), and docs can live in a pattern library (YAML) + Playwright or accept that Storybook is awkward for Django templates unless you add scaffolding.

AI-written summary · about

  1. 0:00Introduction and speaker intro
  2. 1:07Django templates evolution
  3. 4:54Tradeoffs in frontend tools
  4. 5:15Limitations of native Django includes
  5. 7:11Solving include pain points
  6. 8:17Component demo with include contents
  7. 12:54Alternative component packages
  8. 13:58Performance and caching
  9. 14:23Documentation with Django pattern library
  10. 17:50Wagtail PyPI for multi-backend use
  11. 18:59Storybook for component docs
  12. 20:53Framework alignment advice
  13. 21:34Q&A session
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.