Dev Workflows with "Headless" Content Management: Time to Re-Attach the Head!
summary
Claim: a headless CMS can be “re-headed” by shipping renderable primitives and typesafe clients so apps don’t have to anticipate every content change. Built zerv with a CLI that runs zerv sync to codegen a typesafe client, a tiny runtime client using React Query, and a renderable human text component for inline formatting and links. Demo runs in Next.js and Expo on iOS/Android, works end-to-end, Apache-2 licensed and free alpha through April.
AI-written summary · about
chapters (13)
- 0:00Introduction to talk
- 1:47Problems with current workflows
- 3:55Headless CMS advantages
- 4:38Simple CMS demo
- 7:14Type safety challenges
- 8:19Typesafe client setup
- 11:49Re-heading the CMS
- 14:40Human text component
- 16:45Mobile app demo
- 17:49Feature flag use case
- 19:14Open source licensing
- 21:20Business model plans
- 23:10Future of Zerv CMS
related talks
08mHeadless - The Future of CMS Is Here
42mHeadless CMS
22mHow to add a built-in authoring experience to Next.js
28mEverything is a CMS
08mLightning talk from Lenka Vondrackova
02h 51mEnliven UX with React/Redux
22mTweak your page in real time, without leaving the comfort of your editor
21mCreating a Culture of Innovation
