The problem was never only the CMS
A blog that is hard to publish into eventually becomes a marketing liability. The friction is rarely just the editor. It is usually the whole loop: workflow, publishing confidence, discoverability, and whether the team feels ownership over the surface.
We wanted a system that feels like a product, not a hidden content panel. That means the blog should live on the main domain, share the same trust signals, and make the path from draft to live story obvious for non-technical writers.
What changed in the rebuild
- Posts are modeled in code with explicit structure and community metadata.
- Writers can create drafts, publish, and update content from an in-app editor route.
- The public surface is discovery-first, with featured stories, trend rails, and discussion affordances.
The payoff
The best editorial system is the one your team actually wants to return to next week.
Keeping the blog on the same path instead of moving it to a separate host is the right call for trust and SEO continuity.
The point about a blog becoming a product surface really landed. We made the same mistake by treating content ops like an afterthought.