The Big Headless CMS Lie
summary
Payload is positioned as an API-first headless CMS that already has a vanilla React admin and an Express server and now intends to move from Express to Next's App Router to avoid deploying two services. The codebase exposes a local API hitting the DB directly, recently adds Postgres support with Drizzle, and generates TypeScript models for end-to-end types. The pitch claims this consolidation simplifies devops, enables server/client boundaries via server components, and reduces bundler and HMR pain, but it requires breaking changes.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:05Headless CMS pitch flaws
- 3:12Clients and headless benefits
- 4:41The real reason for pushing headless CMS
- 5:22Speaker’s CMS utopia
- 7:07Headless CMS relevance today
- 8:11Payload CMS architecture
- 10:37Payload CMS pain points
- 12:02Bundler ecosystem frustrations
- 13:26Next.js solves Payload problems
- 15:11Payload with Next.js benefits
- 16:33Drawbacks of proposed changes
- 16:56Call to action
