What it is
Marble CMS is a headless content management system written in TypeScript and released under the GNU Affero General Public License v3.0. Its repository carries the description "Super simple headless CMS", and its tagline positions it as simple content management for modern sites. The project sits in the TypeScript and JavaScript ecosystem and is filed under Content & Publishing, specifically the Content Management Systems category. It carries topics covering cms, cms-backend, cms-framework, headless, headless-cms, and marble, with a homepage at marblecms.com and a Discord community alongside a Twitter account. The repository is young, at zero years of age, with 385 stars, 55 forks, and one open issue.
The concrete problem it addresses is publishing articles, product updates, and changelogs to a site without binding that content to a single frontend. Marble separates content authoring from content delivery: writers create and manage posts in the editor, and any site fetches that content through the REST API. Because the backend is decoupled from the presentation layer, the same content can feed a marketing site, a documentation portal, or any other client that can make an HTTP request. Realtime webhooks extend this by letting content changes trigger downstream workflows, so publishing an update can propagate further than the page it originally appeared on.
Key capabilities
- Create, edit, and manage posts inside the editor.
- Organise content with tags and categories.
- Upload and embed images and videos in posts.
- Readability insights inside the editor to check how content reads.
- AI-powered writing suggestions in the editor.
- Realtime webhooks that trigger workflows when content changes.
- Fetch content anywhere through the REST API.
Who uses it and how
- Teams publishing articles, product updates, and changelogs to an existing site, using Marble as the content backend rather than a bundled frontend.
- Developers pulling content into any frontend through the REST API, so the delivery layer stays a separate concern.
- Operators wiring realtime webhooks so that a content change triggers an external workflow.
- Self-hosters following the contributing guide to run Marble locally, which includes database configuration.
- Contributors running the project locally and submitting pull requests under the guidelines in the contributing guide.
Getting started
The README points to the contributing guide for running Marble locally or contributing a feature, covering setup, database configuration, and pull-request guidelines. Community support runs through the project Discord server and the Twitter account, with bugs and feature requests handled as GitHub issues.
When to use it — and when not to
Marble is a reasonable fit for a
