Anonymised case study based on my own systems work. Business names are withheld; no traffic or revenue figures are claimed.
The situation
Four related businesses, spanning IT services, workspace advisory, brand partnerships and personal consulting, each needed a steady flow of useful articles. The owner wanted automation for drafting and publishing, but not at the cost of accuracy: no invented client names, no unverified claims and nothing published without explicit approval.
The approach
1. Static sites, simple hosting. Each website is served as static files by one web server, which keeps pages fast and the attack surface small.
2. A content engine per site. Each site has an engine that creates drafts by category, renders posts into the site's templates, and refreshes the blog index, sitemap and feeds.
3. Approval before publishing. Drafts enter a queue as pending. A separate approval service sends them to the owner through a messaging bot, and only explicit approvals by an allowed method can move an item to published.
4. Guardrails in code. A validator checks every draft before approval and again before publishing. It blocks or flags fabricated engagement claims, named clients or talent, off-topic items, very short posts and filler-heavy text. Slugs are kept short, and each category is limited to a set number of posts per month.
5. Properly licensed images. Featured images come from openly licensed sources, are downloaded to the site rather than hotlinked, and carry a credit line.
6. Safety for older drafts. Drafts created before the guardrails existed were quarantined so they can never be published by accident.
The outcome
The four sites now publish through one consistent, approval-first process, with structured data, sitemaps and licensed images handled automatically and fabricated claims blocked by default.
Lessons
- Automate drafting, not judgement.
- Put editorial rules in code so they apply every time.
- Keep production changes in version control.
FAQ
Does approval slow publishing down? Slightly, but a quick approval step costs far less than correcting a wrong public claim.
Can this work for one website? Yes; the same pattern scales down.
I take on a small number of advisory and hands-on systems engagements each quarter. Connect at virender.in.