ClassicPress

4 of 5 Stars

ClassicPress is a fork of WordPress, launched by people who couldn't stand the block editor. For a while it was mostly WordPress Without Gutenberg, but they've been doing work lately to improve media management and clean up some of the older code that's just kind of grown organically over the years.

=> ClassicPress | the block editor | improve media management

I've experimented with it a bit off and on for a couple of years, and put in the effort to ensure my two (very niche) plugins were compatible. A couple of weeks ago I decided to finally migrate some of my blogs, and it's gone really smoothly!

=> very | niche

Pros

Stable, and familiar to anyone who has used WordPress.
No need to install the Classic Editor plugin!
Nice media features including a column that lets you know where an image is actually being used, even if it's not attached to a post.
Easy migration from WordPress. You upload a plugin that checks for plugins or themes with known compatibility problems, then press a button and it installs ClassicPress.
Most WordPress plugins and themes that don't rely on blocks will work with it.
A ClassicPress plugin directory and theme directory are available (though you currently have to install a plugin to access it from the dashboard).
No need to pass a loyalty test in order to log into the support site.*
It feels snappier so far, but that's just subjective.
Plugin developers don't have to deal with Subversion!

=> Classic Editor plugin | Easy migration from WordPress | plugin directory | theme directory | pass a loyalty test

Cons

The community and plugin/theme ecosystems are a lot smaller.
Plugins and themes that do rely on blocks (or tie deeply into WordPress code that's diverged since the fork) won't work. But you can usually find something comparable to do the job.
Some plugins that are listed on both the ClassicPress and WordPress directories are out of date on the ClassicPress side.
Plugin developers do have to deal with GitHub.

My Experience

Like I said, migration was super-easy. I did a couple of local sites first, then my wife's occasional blog, Feral Tomatoes. Then I had to do some research on plugin compatibility before migrating the behemoth** that is K-Squared Ramblings, which turned out to be a lot simpler than I expected!

=> Feral Tomatoes | K-Squared Ramblings | a lot simpler than I expected

Plugins that work fine so far:

ActivityPub
Antispam Bee (replacing Akismet)
Broken Link Checker (at least in local mode)
Contextual Related Posts (replacing Jetpack Related Posts. YARPP should work too, though I haven't tried it on here yet.)
Statify (replacing Jetpack Stats)
Syndication Links
WP Super Cache
Wordfence Security...once I turned off the scan options for modified WordPress core files, anyway. (It thought my site was reaaaaally broken at first!) There's some debate over how well it works with CP, so I'm going to be keeping an eye on it to see if I run into any other problems.

Various IndieWeb and ActivityPub plugins are reported to be compatible, and they didn't deactivate when I converted the site, but I haven't really tested them yet.

IndieWeb
Webmention
WebFinger
NodeInfo(2)

Incompatible plugins:

Search Regex. I haven't used it in a while, though, so I figure I'll wait until I need it before looking for a replacement.
Yoast SEO. It's overkill*** for what I want anyway, so I don't feel too bad about replacing it. The Classic SEO plugin includes all the features I'm using Yoast for, and W3P SEO offers most of them. I may still switch to a collection of smaller, focused plugins in the long run, but I was able to migrate immediately by just swapping in Classic SEO!

=> Search Regex | Yoast SEO | Classic SEO

I might still move the older posts to Eleventy, but at least it's on a simpler platform now than it used to be, and it's shown no sign of new problems yet.

That leaves one more gigantic, complicated blog: Speed Force. It's got some additional complications like co-authors so that more than one person can be credited on a single post, and subscriptions through Jetpack. So it's going to need some more research before I migrate that one.

=> Speed Force

Notes

Notably, ClassicPress is confident that they are safe from any potential antagonstic action from Automattic. They're a fork, not a hosting provider (and got name-dropped in a forks-are-OK post). The GPL protects the right to use the code. The name is different enough to avoid trademark claims. My main concern would be if they were to lose WordPress API access, but they already have their own update servers and directory up and running.

=> safe from any potential antagonstic action from Automattic | forks-are-OK post | My main concern | already have their own update servers and directory

- It's been around for 22 years. I've been moving posts that are more garden than stream from my main blog to other parts of my site for a while now (this is also why I'm writing this here), and started cleaning out old stuff that doesn't need the longevity (links without commentary, for instance, especially when the remote link is long-dead anyway) to make it easier to migrate. Even after all that, there were still more than 3,200 posts. So you can see why I might've been a bit nervous!

=> more garden than stream | my main blog | cleaning out old stuff

** I'm not using the analytics or the automatic linking or anything most people think of as "SEO" -- it was just a convenient choice back in the day to build a sitemap and add metadata for link previews and the occasional noindex tag or canonical link.

October 17: Initial publication. October 26: Added alternatives to Yoast. October 29: Update now that I've successfully migrated K-Squared Ramblings.

— Kelson Vibber, 2024-10-29

ClassicPress

Pros

Cons

My Experience

Notes

External

Related Posts and Tags