WordPress 7.0 putting AI in core split the community louder than anything since Gutenberg. Forum threads filled with developers announcing their exit plans, and the name on most of those exit plans is ClassicPress — the community fork that keeps WordPress’s engine without the block editor or the AI ambitions (the “remove the AI” discussions on their own forums are worth reading to feel the mood). So let’s answer the question honestly: ClassicPress vs WordPress in 2026 — should you actually jump ship?
I run WordPress 7.0 with its AI features enabled and reviewed, so you know my bias upfront. Here’s my attempt at a fair answer anyway.
The Case for ClassicPress (It’s Real)
- Philosophical clarity. If you believe a CMS should be a CMS — no bundled AI clients, no block-editor churn — ClassicPress is that, on purpose, forever. That’s a legitimate position, not Luddism.
- Stability as a feature. Fewer moving parts, fewer surprise redesigns of your admin, fewer “core now does X” emails to send clients.
- Lighter by default. No AI infrastructure means nothing to disable and no temptation for plugins to lean on it.
The Case Against Jumping (Also Real)
- The ecosystem is the product. WordPress’s superpower was never the core — it’s the plugins, themes, hosting integrations, tutorials, and hireable developers. A fork inherits a snapshot of that, then drifts. Every year the compatibility gap widens.
- The AI is opt-in anyway. Practical reality from my own install: connect no API key, and WordPress 7.0’s AI does precisely nothing. “Disable the connectors” is a one-minute conversation, not a migration project.
- Client sites are not protest venues. Your ideology shouldn’t become a client’s maintenance problem. They need updates, developers, and plugin support for the next decade — the boring, safe bet is the mainstream platform.
ClassicPress vs WordPress: My Verdict
For a personal site owned by a developer with strong convictions: sure, ClassicPress is a coherent choice, and honestly the ecosystem benefits from a serious fork keeping core honest. For client work and businesses: I can’t recommend it. The risk isn’t ClassicPress being bad — it’s betting someone else’s website on a smaller community out-maintaining the biggest CMS project on earth. That bet has gone badly for nearly every CMS fork in history.
My actual advice mirrors what I did: stay on WordPress, leave the AI features unconnected if they bother you, keep your plugin stack audited, and revisit the question in a year when both projects have shown their cards. Jumping platforms out of annoyance is how people end up maintaining two problems instead of one — and annoyance, unlike a migration, is free to sit with for a while.
