Hi everyone
CMS expectations have changed a lot over the last few years, largely because Next.js raised the bar.
You’d think by late 2025 we’d be past the era of “purge everything and hope nothing explodes”, but somehow… we’re not. We still see teams invalidating entire sites because one product description changed. Lovingly judging, but judging nonetheless.
With Next.js, this shouldn’t be happening.
Route-level revalidation is table stakes now. Change one document, and only its related routes rebuild. Update one component, and only the pages using it refresh. The CMS should understand dependencies instead of treating every update like a meteor strike.
And yet we still run into teams:
- Purging all routes as a lifestyle choice
- Deploying five times because “preview isn’t updating”
- Wondering why the homepage still shows 2022 data
- Blaming the CMS when the real culprit is the caching layer
Next.js already gives us predictable cache behaviour and granular control. A CMS fires a webhook, Next.js receives the signal, the exact route gets revalidated, and the frontend updates cleanly and instantly.
From there, a few things become non-negotiable for a CMS in 2026
- Precise cache invalidation that actually works with Next.js
- Real-time previews instead of “save and pray”
- Bulk releases & scheduling without cron jobs or late-night pings
- Schema-aware AI that helps maintain content, not just rewrite text
- Visual editing with guardrails, not design chaos
- Instant rollback, because mistakes happen
We wrote a longer breakdown on how CMS expectations have shifted and why certain platforms integrate more cleanly with modern Next.js setups than others.
Read here: The state of headless CMS
Curious how others here are handling cache revalidation and previews at scale. What’s been solid for you and what’s still painful?