Managing Content with Django
summary
Compares two concrete stacks: Django CMS (minimal admin skin, plugin-driven, uses Django Filer, stronger multilingual support, good for data-rich apps and frontend editing) versus Wagtail (feature-rich, visual media manager, approval/workflow, page-first model with streamfields). Demonstrations use each CMS’s default demo rather than bespoke projects; research phase recommendations (months for complex sites), tradeoffs around composable blocks, page types, data vs content, and thumbnailing/plugins are explained with practical pros and cons. Watch if choosing between these two.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:46Why Django for CMS
- 3:32Research in CMS projects
- 6:21Content creators' needs
- 9:32Django CMS vs Wagtail
- 18:17Editing with blocks
- 22:32Page types and structures
- 26:28Data vs content in CMS
- 29:42Media management challenges
- 33:22Wagtail vs Django CMS
- 36:38Q&A
related talks
31mComparing Wagtail, Django CMS and Mezzanine
21mWagtail CMS - Making Django More User (and Developer) Friendly
38mdjango-cms: Friends don't let friends use Drupal.
29mWagtail - Yet Another Django CMS
30m"Wagtail: The Python CMS Taking the World by Storm"
22mSpicing up Django: An Introduction to Mezzanine CMS
40mEntering the World of CMS with Wagtail with Michael Riley
30mWhy would a new developer choose Django?