A newsroom that feeds the whole estate

What it is

WordPress is the most widely used publishing system on the web. Most people know it as a blog engine, but underneath it is a solid editorial tool: drafts, revisions, review before publishing, scheduled posts, categories, and user roles that separate the people who write from the people who approve.

It also has a REST API. Every post, category and tag can be read by another program as structured data. That is the part that turns a website into a newsroom for other sites.

Why I run it instead of the SaaS alternative

Hosted platforms such as Substack, Medium, Squarespace or WordPress.com remove almost all of the maintenance, and for a writer who just wants to publish, that is a good deal. I recommend them to people who do not want to look after a server.

I self-host because the newsroom is part of a system, not a standalone site. Other sites on the estate pull headlines from it, scheduled agents write to it, and I want the API, the database and the publishing schedule under my control. On a hosted platform I would be working within whatever integration the vendor allows. Here the content is mine, the address is mine, and nothing changes unless I change it.

The honest counterweight: WordPress is a popular target precisely because it is everywhere. Self-hosting it means taking updates, plugins and accounts seriously. That is a cost I accept knowingly, not one I pretend away.

How it is set up here

1. Its own containers and database. WordPress and its database run separately from every other service on the estate server.
2. Behind the single edge. Traffic arrives through the same nginx edge as everything else, which handles TLS and routing.
3. Editorial workflow. Posts go through drafts and review, and are scheduled to publish at set times rather than whenever they happen to be finished.
4. AI agents keep it current. Scheduled agents built on the Anthropic API draft and file stories, with every job's cost accounted for. The newsroom does not go stale because I was busy.
5. An API for the rest of the estate. Other sites read the latest headlines through the REST API, so news published once appears wherever it is relevant.
6. Backed up and watched. The database leaves the server nightly, and the site is in the five-minute content checks.

What it replaces

• Hosted blogging platforms for content that other systems need to consume.
• Copying the same announcement by hand onto several websites.
• A news section that stops being updated after the launch month.

What it costs to run is server capacity, a disciplined update routine, and a short list of plugins kept short on purpose. Each plugin is more code to patch, so every one has to justify itself.

What I would do for a client

If you already run WordPress, the first job is an audit: version and plugin currency, who has administrator access and whether they still should, what the backups actually contain, and whether a restore has ever been tested. Neglected WordPress sites tend to fail in the same few ways, and they are cheap to fix before they matter.

If you need a publishing hub, one place where announcements are written once and appear across several sites, apps or screens, I would build it as it runs here: a clean editorial workflow, the REST API as the distribution layer, single sign-on for editors, and automation only where it removes real work. If you just need a blog, I may well tell you to use a hosted one.

Questions people ask