Picture this: you’re a marketing lead at a growing SaaS company. Your blog posts need to feed the main site, a Next.js landing page, docs in a separate repo, and even an app’s in-app feed. One frontend rewrite later, and half your content crumbles — shortcodes vanish, layouts bleed, previews glitch. That’s the quiet nightmare WordPress traps you in when it stops being ‘just a blog’ and becomes a content system.
It’s not about WP being broken. Far from it. But recommending it as the default for modern content systems? That’s where the reflex kicks in — and it’s costing teams real time, real frustration.
When ‘Just Use WordPress’ Backfires
WordPress shines for theme-driven sites. Quick launch, familiar editors, ecosystem galore. But shift to API-first worlds — multi-frontends, portable data, preview isolation — and cracks show.
The author nails it:
WordPress is excellent at powering WordPress sites. I just do not think that automatically makes it the best foundation for API-first, multi-frontend, multi-site content architecture.
Spot on. WP’s strength — coupled rendering — turns foe when you decouple. Plugins pile up: one for fields, another for previews, webhooks, caching. Suddenly, your ‘simple CMS’ is a fragile plugin treaty. One update, and poof — editorial trust evaporates.
Here’s my take, the one nobody’s saying loud enough: this mirrors jQuery’s fall. Remember? It glued the early web together, but as frameworks demanded modular JS, jQuery became baggage — powerful, but assuming a DOM nobody owned anymore. WordPress assumes a theme, a site, a renderer. Modern content assumes data flows everywhere. WP’s fighting the tide.
Why Does Content Portability Suddenly Matter?
Teams hit this wall when ‘a website’ morphs into a platform. Same content powers:
-
Next.js hero sections
-
Docs sites (maybe Astro or Docusaurus)
-
Mobile apps
-
Client microsites
-
Internal dashboards
WP stretches — REST API, Gutenberg blocks, ACF plugins. But structured? Ha. Try migrating: shortcodes everywhere, theme HTML baked in, layouts that only render right in one place. It’s ‘structured’ until export day.
And previews? Editors hate mystery. They demand the real frontend, draft fidelity, no leaks. WP previews? Custom routes, tokens, cache hacks — bolted on. No wonder workflows shatter on frontend pivots.
But — and this is key — WP borrowed ideas still rule. Blocks as data. Schemas. The author built HTMLess lifting those, ditching WP’s deployment baggage. Content management splits from delivery, previews get boundaries: public cache vs. private drafts vs. scoped peeks. Boring? No. That’s architecture winning.
Short version: WP postpones complexity. Headless natives reduce it.
Is HTMLess the Anti-WordPress Fix?
Not quite a WP killer — it’s open-source, schema-first, preview-native. Core assumes multi-site isolation, scoped tokens, property filtering. No plugin roulette.
Why build it? Author got fed up watching teams ‘stretch’ WP into headless. Result: accidental stacks where schema validation’s a retrofit, not DNA.
Look, WP’s PR machine spins it as ‘headless ready’ forever. Bull. ‘Can do it’ isn’t ‘best for it.’ Enterprises quietly swap for Sanity, Contentful, or homebrews when scale hits — portability trumps familiarity.
My bold call: in three years, 70% of new content platforms skip WP entirely. Why? AI content gen demands clean data pipes. Frontend multiplicity is table stakes. Plugin debt? Unbearable at scale.
The Real Cost to Your Team
Frontline editors suffer first. Trustworthy previews? Gone. Portable content? Dream on. Devs? Glued fixing glue.
WP wins for solo blogs, small teams, theme fidelity. But content platforms? Pick tools born for APIs, not retrofitted.
Wandered there myself — recommended WP on autopilot once. Next project: frontend swap killed half the posts. Never again.
Shift’s here. Schema-first CMSes aren’t hype; they’re sanity.
🧬 Related Insights
- Read more: PURESLOP.md: The CLI Sabotaging Your AI Coder on Purpose
- Read more: Next.js 16 i18n: 10 Languages, Zero Regrets
Frequently Asked Questions
Should I ditch WordPress for a headless CMS?
If your content spans multiple frontends or needs true portability, yes — start evaluating now. Stick with WP for simple, theme-bound sites.
What makes HTMLess different from WordPress?
Built-in schema validation, isolated previews, multi-site support — no plugins needed. It’s data-first, not page-first.
When is WordPress still the best CMS choice?
Quick blogs, familiar teams, single-site themes. Anywhere speed-to-launch beats long-term flexibility.
