- New site. Started with a fresh WordPress install.
- Got WP site set up.
- Installed Indieweb plugins and a few others. Avoided using WordPress owned plugins like Jetpack and Akismet. Found alternatives.
- Wrote some posts.
- Rediscovered ClassicPress. Decided this was the best time to try ClassicPress before I have too much content and before I add too many more plugins.
- CP is compatible with most WP plugins that will run on ver. 4.9.9 or older. Checked all plugins.
- Just to be safe, prior to conversion, I disabled almost all plugins including all Indieweb plugins.
- Installed the ClassicPress migration plugin.
- Followed instructions on that page for migration plugin.
- Plugin detected no conflicts.
- Yea! Nothing broke. No errors. Utterly painless.
- Started reactivating plugins disabled in step #7 above.
- Everything works. The reactivation of the Indieweb WP plugins caused no errors that I can detect. But, the site being so new, they remain untested.
Why Convert to ClassicPress?
If you don’t trust the direction WordPress is headed (ie. block editor and more commerce oriented). Combined with all you need is a full featured blog.
What have we learned?
My web host does not support ClassicPress auto installs. However I can 1 click install WordPress and very easily convert it to ClassicPress right away via that migration plugin.