Building a Wagtail CMS Experience that Editors Love with Michael Trythall
summary
Shows concrete content modeling: use Wagtail pages models snippets, map nouns and relationships, and capture requirements in spreadsheets or diagrams. Enforce rules like limit nesting to 3 levels and guardrails to prevent errors with guardrails (no inaccessible H1s, no 15-card rows). Balance composability and structure with predefined cards and limited block lists, prototype CMS fields in Figma, and iterate — examples include a landing‑page pattern (intro + three features) and a dogfooded AI page with many blocks.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:17Why CMSs fail
- 8:09Content architecture research
- 16:50Content modeling in Wagtail
- 23:13Composability vs structure
- 33:42Flexibility and consistency
- 38:21CMS maintenance best practices
- 40:51Q&A
related talks
21mWagtail CMS - Making Django More User (and Developer) Friendly
29mWagtail - Yet Another Django CMS
25mAtomic Wagtail
30m"Wagtail: The Python CMS Taking the World by Storm"
31mComparing Wagtail, Django CMS and Mezzanine
40mManaging Content with Django
30mWhy and When to Use Wagtail?
06mScale Your Website With Flexible Content Models