The Newsroom Block

The problem

A page called Blog is not a blog. Publishing properly means somewhere to write and schedule, comments that do not turn into a spam problem, search that can still find a two-year-old post, and some idea of whether any of it was read. The usual answers are a stack of WordPress plugins, each with its own subscription and its own security patches, or paying a developer to build the same thing again from scratch on every site.

What got built

The whole system ships inside your site's own codebase rather than bolting on at runtime, so it loads at the same speed as the rest of the site, wears your fonts and colours, and gives your team one place to log in. Underneath, it is a single package installed into each site instead of three copies quietly drifting apart, which is what makes a fix or a new feature reach every site at once. Behaviour is shared and appearance is not: a comment thread works identically everywhere, while the story layout, the colours, and the words your site uses for things are yours.

Details worth naming

• Write, schedule, and publish, with roles so the people who should be able to hit publish can and everybody else cannot.
• Moderation that assumes the worst: every new account posts through review until one of its comments is approved, so a spam wave never reaches the page.
• Search across the entire archive, indexed and ranked when a story is published, with no third-party search box to rent.
• Readership figures from a first-party beacon: what was read and for how long, without adding somebody else's tracker to your site.
• Coming off WordPress is a supported path, not a rescue mission. The old posts come across.
• Styled entirely through your site's own colours and fonts, so it reads as your publication rather than a template somebody else also bought.