Everything is a CMS
summary
Argues that any system with an API or file-write can be a CMS and demonstrates building an engine that normalizes drivers for Contentful, Trello and similar sources so Next.js pages call a single interface. Shows two engine patterns: an API engine (GraphQL/REST) and a file engine with a writer/reader that runs via npm run import and produces markdown consumed by getStaticProps. Emphasizes picking a few preferred tools and avoiding duplicated data-source logic.
AI-written summary · about
chapters (8)
- 0:00Start
- 8:54Evaluation Criteria
- 11:59Project/Task Management
- 12:17SPREADSHEETS!!!
- 12:31Cloud File Storage
- 12:44Local Apps, Editors, and Files
- 19:39Sound familiar?
- 25:12Bring it in!
related talks
24mThe Future of Editing Websites
18mThe Big Headless CMS Lie
15mBuilding Modern CMS Driven Web Applications with Next.js
21mCreating a Culture of Innovation
12mCMS and JAMstack: A Tale of Innovation in Web Development
31mAngular + CMS = ❤️
52mThe Promise and Peril of Scriptable Software
08mHeadless - The Future of CMS Is Here
