Zenblog

Zenblog is a minimalist, headless content management system built specifically for developer blogs and multi-publication management. It decouples the editorial environment from the public-facing site, exposing structured markdown and metadata via a type-safe TypeScript client and REST API. For self-hosters, this architectural separation isolates the administration dashboard and underlying database from direct web traffic.

Why Zenblog instead of WordPress

WordPress couples content authoring, database queries, and HTML rendering inside a single PHP runtime. Operating WordPress on a homelab server requires maintaining a public-facing PHP environment that exposes administrative paths, legacy hooks, and third-party plugins to continuous web probing. Unvetted plugins frequently leak visitor telemetry, initiate external CDN calls, or introduce attack vectors into the host system. Zenblog eliminates this exposure by functioning purely as an internal content store. Public readers interact solely with an independent frontend, such as a static Next.js or Astro deployment, while the editorial dashboard and its PostgreSQL database remain shielded behind local network boundaries.

The trade-off is straightforward. WordPress provides out-of-the-box convenience with prebuilt themes, page builders, and commenting systems. Zenblog renders no public frontend on its own; administrators must deploy a separate client application to display posts. In return, self-hosting operators retain complete authority over reader privacy and client-side code. There are no unexpected database queries, tracking cookies, or external assets loaded without explicit configuration.

What it does well

• Network boundary isolation: Keeping editorial administration detached from public presentation prevents unauthorized login probing and eliminates theme-level vulnerabilities.
• Relational data custody: Articles, tags, categories, and author records reside in standard PostgreSQL, enabling direct schema inspection, automated backups, and zero proprietary lock-in.
• Multi-publication hosting: A single instance manages multiple blogs and custom domains simultaneously, removing the need to orchestrate multiple containers or complex multisite networks.
• Type-safe integration: A dedicated TypeScript client and OpenAPI specifications let administrators pull posts into static site generators with compile-time verification.