Marble CMS

Marble CMS is an open-source headless content management system tailored for blogs, changelogs, and editorial documentation. Instead of imposing complex schema builders or monolithic web servers, it pairs an opinionated content model with a lightweight REST API and webhook-triggered static builds. Writers manage articles in a clean interface while frontends query typed JSON without runtime database overhead.

Why Marble CMS instead of WordPress

WordPress couples content storage with server-side page rendering, running PHP scripts and SQL queries for every visitor request unless masked by caching layers. Over time, themes and dynamic database lookups introduce latency to public pages and admin dashboards alike. Marble CMS decouples writing from presentation, exposing content through REST endpoints designed for static site generators such as Astro or Next.js. Page generation happens during build cycles or incremental static regeneration, serving flat assets without touching a database on visitor arrival.

Operational overhead shows a similar divide. Running WordPress in a homelab requires orchestrating PHP-FPM, a reverse proxy, and a MySQL instance that requires ongoing maintenance. Marble CMS packages editorial administration into a TypeScript service backed by PostgreSQL, avoiding the fragile plugin dependency chains that degrade WordPress performance. While it lacks WordPress's plugin library, its direct webhook dispatches and REST pagination provide immediate static rebuilds whenever an author publishes an update.

What it does well

• Pre-structured content schema: centers on posts, authors, categories, tags, and custom fields, eliminating hours spent modeling relational schemas from scratch.
• Dual-format content responses: delivers post bodies as pre-rendered HTML or Markdown via a format query parameter, reducing client-side parsing work.
• Instant webhook triggers: dispatches HTTP payloads with cryptographic signatures to revalidate static frameworks the moment content changes.
• Integrated media management: accepts image, video, audio, and document uploads while storing dimensions and generating stable asset URLs.
• Agent-ready API and MCP: includes a Model Context Protocol server that allows AI coding assistants in Cursor or Claude to draft and edit posts programmatically.
• Clean JSON archive exports: packages workspace posts, authors, taxonomy labels, and media references into a single JSON file for offline backups.