





Hi r/cms,
I’ve been working on a small, lightweight, headless CMS aimed at solving the issue of developer, client hand off. A UI designed for non-technical clients to update content safely, and a shared space for devs or admins to review changes.
The goal is to keep the editing experience safe for non‑technical users while giving developers full control over structure and delivery. It’s schema‑driven, returns flat JSON via a simple REST API, and avoids rebuilds entirely.
Current functionality includes schema‑based content types, Text, JSON, HTML, image validation, draft -> review -> publish workflow, version history, audit logs, localization, and role‑based access. The editor UI is intentionally minimal to reduce the risk of layout‑breaking changes.
For previewing draft content, I’m using short‑lived preview tokens (5–15 minutes) thatis passed in a query string to the designated url, then passed to the public API endpoint that returns the published content and it overrides the production api key and returns draft content for that session. The goal is to let editors preview on the production domain safely and easily.
Tech stack is .NET for the API, MongoDB, and an Angular/Tailwind dashboard. Everything is designed to stay lightweight and predictable for multi‑project setups.
I’d love to hear thoughts from people who work with CMS tools regularly, especially around schema design, validation workflows, and what you consider essential for safe client editing. Happy to answer questions or share further details on the app.
If anyone wants to try it out, feel free to DM me.
Hey r/webdev !
I’ve been working on a small headless CMS aimed at solving a problem I kept running into with client projects: content edits breaking layouts or triggering rebuilds. The idea is to make content updates instant and safe without limiting developers.
Right now it supports schema‑driven editing, Text, JSON, HTML, image validation, draft -> review -> publish workflow, version history, audit logs, localization, and role‑based access. Everything is delivered through a simple REST API which returns a flat JSON response.
For previewing draft content, I’m using short‑lived preview tokens (5–15 minutes) thatis passed in a query string to the designated url, then passed to the public API endpoint that returns the published content and it overrides the production api key and returns draft content for that session. The goal is to let editors preview on the production domain safely and easily.
Still early, but it’s functional and I’m refining the workflow. I’d love to hear what you think especially around the editing experience, API design, and anything you’d expect from a CMS built for developers.
Built with:
If anyone wants to try it out, feel free to DM me.
Happy to answer questions.