Case study · 2026
Publishing portal
Publishing without opening WordPress. Content syncs from its real sources, waits for approval and ships in 14 languages.
- steps from source to site
- 5steps from source to site
- content modules at launch
- 20content modules at launch
- lines of code, AI-first
- ~58,000lines of code, AI-first
- languages per release
- 14languages per release
- Role
- Designed it and built it with the second engineer on my team
- Users
- Designers, writers and agencies across marketing
- Timeline
- First commit Jun 8, 2026 · live in July
- Stack
- Custom WordPress plugin, automated importers, Jira and Slack integrations, AI-first development
01·The problem
Before July 2026.
Every change went into WordPress by hand, and a lot of content never made it to the site.
Thousands of pages, by hand
Product and integration pages alone ran into the thousands across 14 languages. Every update meant opening WordPress, page by page.
Engineers as the bottleneck
Content requests queued behind development work, and during the rebuild they could wait for weeks.
02·How it works
Content comes from where it lives. People only approve.
- 1
Sync from the source
Product data, integrations, webinars and press sync from where they really live.
- 2
Import
Automated importers map each item to a structured content type.
- 3
Approve
Changes wait for review, with role-based access.
- 4
Publish
Approved items ship to the site, in every language.
- 5
Audit
Every change is logged in Jira and announced in Slack.
03·Timeline
From first commit to production in weeks.
- Jun 8, 2026First commit. AI-first development, about 58,000 lines of code.
- Jul 2026In production, with 20 content modules.
- Aug 2026Most changes now arrive through automated importers instead of by hand.
- Sep 2026A hotfix pipeline: urgent fixes go from preprod to production through the portal, with re-authentication, a human-confirmed link and an audit trail.
04·What it unlocked
The point was never just the feature.
Engineers build again
Content changes stopped competing with development work, so the two engineers could ship tools instead of edits.
Self-service, with guardrails
Teams publish on their own, with approvals, role-based access and an audit trail for every change.
Safe urgent fixes
Even hotfixes go through the portal, with a confirmed link between preprod and production and a full record.
More case studies
Every figure on this page is public or my own measurement: Chrome UX Report, PageSpeed captures, git and the site's own content. The company's business data stays private.