The ultimate CMS vs Framework showdown
summary
Compares concrete choices: uses Plone, Django, Drupal and WordPress examples, cites WordPress ~30% market share and government use of Plone, shows wireframes as signal you’re building an app, contrasts static generators (Sphinx) vs frameworks (Django/Flask) and CMSs (Mezzanine/Django CMS), describes building a school timetable as crawlable pages for Google, describes integration techniques used—domain split, iframes/Ajax, proxying and a custom whiskey middleware reposts POST data approach—and reports these integrations can work but add hidden complexity and scaling limits.
AI-written summary · about
chapters (16)
- 0:00Start
- 2:34Python family tree(web)
- 5:50What is a CMS?
- 6:10It's an app
- 6:43It's a "big" framework
- 10:48What about django CMS?
- 11:20Am I making an "app"?
- 13:43Separation of concerns
- 14:58Developers blog
- 15:37An app/startup
- 16:18Simple Blog
- 16:39Large content site
- 17:18Web consultancy
- 17:57The customisation cliff
- 19:01Framework vs CMS
- 23:55Summary
related talks
32mState of the CMS
46mCMS Speed Dating: Find the Right CMS for Your Web Project
38mdjango-cms: Friends don't let friends use Drupal.
38mIs Drupal the Best Choice?
42mHeadless CMS
29mHow Django helped us make a better conference website
18mA framework author's case against frameworks
06mWordPress Meets WASM: Full Power of the CMS In Any...