Dev Workflows with "Headless" Content Management: Time to Re-Attach the Head!

Teams maintain both an application codebase and its user database, while marketers, designers, and executives also need to change application content. When developers must make every change and deploy it, the process slows the team and takes time from product work. Vicente proposes a CMS dashboard so nontechnical teammates can manage content directly.

Traditional CMS platforms such as WordPress combine content management with the web application, which makes serving App Store applications harder and limits developers’ choice of tools. A headless CMS separates the dashboard and content database from the application and exposes content through an API. In a demo of Zerv, Vicente creates a text field and a reusable FAQ schema, then explains how a CLI can read the schema and generate a type-safe client.

A headless API still leaves developers to anticipate and manually render every content type. Vicente demonstrates Zerv’s experimental Human Text field, which lets a marketing editor add bold text and links without treating the content as a plain string. After syncing the schema and installing a rendering package, he shows the content in a React Native app on iPhone and Android, with developers retaining control over rendering and behavior.

Vicente describes possible future additions, including page components, images, video, low-code features, authentication, and real-time updates. He says Zerv is open source under Apache 2.0 and plans to support the project with a paid hosted service, while keeping the alpha free for at least six months and inviting side-project use and feedback. He cautions that it has rough edges and is not ready for production business use.