Catching up with ClassicPress
In our previous article published late last year, “ClassicPress Beta is now available – should we adopt it?“, we took a look at the new WordPress fork called ClassicPress, which essentially provides a normal WordPress installation but without the new Gutenberg block editor.
In that article we concluded that ClassicPress was an exciting development in the WordPress ecosystem, but we didn’t yet feel able to switch any client sites from WordPress to ClassicPress, primarily because of the lack of a security plugin that could scan the ClassicPress core installation and report any ‘dodgy’ files – something we normally use WordFence for.
And to be honest, we were also concerned about whether the ClassicPress project would actually succeed in gaining enough traction not to disappear without warning a few months down the line. However, despite our uncertainty, we still took steps to ensure that all ZigPress free plugins in the WordPress repository worked correctly on ClassicPress installations, as a way of giving a little support to the project.
So how is ClassicPress doing now?
Now, almost four months later, ClassicPress has reached its first non-beta release (1.0.1 in fact) and as we had hoped, there is now a free security plugin available that scans ClassicPress core files on a daily basis, reporting any discrepancies via email. That plugin is the excellent Shield Security.
During that time I have participated in discussions in the ClassicPress forums, helping out with testing and bug reporting and offering opinions, and have gradually come to the conclusion that the growing team behind ClassicPress are serious about making it succeed as a long-term, indeed permanent, replacement for WordPress.
The other issue discussed in our previous article was that the MainWP WordPress installation management system was not able to automatically update ClassicPress installations (though it can update themes and plugins on ClassicPress installations), and it’s only fair to point out that this situation hasn’t yet changed.
So, has ZigPress’s view about using ClassicPress on live sites changed since our previous article was published?
Yes, it has.
We’ve made the decision that certain ZigPress client sites will be migrated from WordPress to ClassicPress, and by ‘certain’ we mean:
- sites where the client is not very technically minded and happy to be guided by us regarding the back-end user experience that their site provides
- sites where the client leaves all content editing to ZigPress
- sites where content editing is based entirely on Advanced Custom Fields Pro and the Gutenberg block editor would be completely superfluous for that reason.
Other client sites, including those where the client is more technical and is very much engaged in the WordPress experience, will be left as they are for now (since it’s possible that the client will ask to use Gutenberg at some point), and we will discuss the ClassicPress option with those clients a little further down the line.
ZigPress also runs a small number of non-client sites (i.e. our own projects), and these will all be migrated to ClassicPress in due course – including this site.
When we are asked to submit proposals for new website projects, we will assess the requirements on a case-by-case basis when deciding whether to specify WordPress or ClassicPress as our chosen platform for the project.
So in conclusion, we’re happy to announce that ZigPress is now committed to ClassicPress as a key platform in our business activities (though not the only platform of course), and we hope and expect that the ClassicPress project will go from strength to strength in the coming months.
If you’re a WordPress developer who would rather work without the block editor, we now feel we can recommend ClassicPress as a genuine alternative that is well worth examining.
And if you work for MainWP, we would like to encourage you to support this new growing platform!