State of the CMS
summary
Compares concrete CMS choices and tradeoffs: WordPress holding 75% market share but plugins can hide data (two‑times base64 example) and make handoff hard; Webflow that publishes but whose content is export limited to CSV or API; git‑based systems (Netlify CMS, Tina) that publish via commits; headless options (GraphCMS, Strapi) and platforms (Sanity, Contember) that raise monthly costs (examples starting ~$90–$400) but reduce ops pain. Calls out the $1.5T cost of not updating software and gives a simple vendor‑dependence vs maintainability index to choose by long‑term maintenance.
AI-written summary · about
chapters (8)
- 0:00Start
- 7:56The Missing Feature
- 11:02Git-Based Cms
- 15:08Flood Files Cms
- 16:58How Hard Is It To Switch to Something Else
- 17:50Classic Cms
- 18:21Rating for Classic Cms
- 21:48Managed Hosting
related talks
46mCMS Speed Dating: Find the Right CMS for Your Web Project
23mIs FOSS losing to SaaS? Data from the CMS battleground
28mThe ultimate CMS vs Framework showdown
14mIt's a Jungle Out There: The Security State of CMS Platforms
42mHeadless CMS
32mThe Evolution and Future of Content Publishing
28mEverything is a CMS
07mWhy Shopify and WordPress Suck