On my personal website, I do occasionally talk about the future of WordPress and my issues in developing plugins for my own use. But I also maintain the Gadget Wisdom infrastructure. So, recently, I wrote about switching my personal site to ClassicPress. I’m going to continue to write about that there, but wanted to cover a little of this here, in a different context.

Recent drama at WordPress finds a lot of people exploring exits from the community. WordPress drama is not a new thing. There were many times during the transition from WordPress 4.9 to 5.0 I considered leaving. But having built many things on top of a platform, I opted to remain.

More recently, I switched this site over to ClassicPress as well, a fork of WordPress. ClassicPress has a simple plugin to migrate WordPress instances…it will even let you revert back if need be. So, while the drama over on the WordPress side may continue, I get to keep the platform without the elements that frustrate me. There are concerns about ClassicPress as well. WordPress powers a significant percentage of identifiable websites. Forks of projects do not always survive, but there are many examples where they do.

ClassicPress is a fork of WordPress that removes the block editor…WordPress’s big change in Version 5. It retains a traditional editor, which many people prefer, and continues to iterate in that direction. As a result, it is leaner and somewhat more performative. It is WordPress as it used to be…but also with improvements…but in a completely different direction than WordPress while maintaining compatibility. The only problem is that the project doesn’t get the attention it could, especially now that people are questioning the governance of WordPress. But it is WordPress…like it used to be…before it went hard in another direction.