Entering the World of CMS with Wagtail with Michael Riley
summary
Wagtail demands code-first models not UI hacks: pages and articles become Django models with foreign keys for images and authors, rich text fields and StreamField blocks for flexible content. Production advice is concrete: frontload CDN caching, implement cache purging on updates, instrument with APM/observability, and use Redis/Valky carefully — a rule of thumb around 2,000 requests/sec per Redis before stampedes occur. Real failures include a cache flush causing outage at ~100k requests; Draftail serves as the editor.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:12Good CMS for developers
- 7:04Wagtail’s content modeling
- 8:48Content writer workflows
- 15:52User scale and CDN caching
- 18:24Caching and performance tips
- 21:40Monitoring and observability
- 25:08AI bots and scrapers protection
- 27:03Q&A
related talks
29mWagtail - Yet Another Django CMS
30m"Wagtail: The Python CMS Taking the World by Storm"
21mWagtail CMS - Making Django More User (and Developer) Friendly
31mComparing Wagtail, Django CMS and Mezzanine
40mManaging Content with Django
25mAtomic Wagtail
30mWhy and When to Use Wagtail?
01h 39mTUTORIAL: Parlez-vous Wagtail? Internalization for Python/Django developers