THANK YOU for this site-saver plugin

I wanted to take the time to sign-in just to say thank you! I was thrilled that someone has also started a WordPress fork (ClassicPress) but I’m also relieved that the Classic Editor plugin is available so that now, I won’t have to worry about my self-hosted websites – that rely on the WordPress CMS – breaking because of Gutenberg.

I’m not a coder/developer but I did learn enough coding to be able to make changes to my purchased WordPress themes that are the design support for all of my WP sites, which is why I liked WordPress over any other CMS – the flexibility it offers to us “average” end-users (well offerED until Gutenberg). The classic editing features in WordPress were just SO easy to use and the Classic Editor plugin restores those features. My first time using WordPress was 10 years ago, before I knew anything about coding or designing/styling websites, and the classic WordPress editor environment made the entire process of writing content and building websites, enjoyable.

When I was alerted about Gutenberg, I tested it multiple times, starting at first release, and then have continued testing Gutenberg as it has been further developed. I didn’t like Gutenberg at first release, and I don’t like it now (it’s not intuitive, is buggy and cumbersome, and is just no fun at all to work with, and it makes typing an actual CHORE). So I decided that removing WordPress from my server and replacing it with a more user-friendly and reliable CMS was the best course for my websites before the arrival of WP v5 Gutenberg!

I have to add that Classic Editor plugin is a SITE SAVER! The Classic Editor plugin is currently installed on ALL of my WordPress-powered sites (all 4 of them) to protect them from the Gutenberg “bully”.

Now I’ll wait patiently to see what happens with the ClassicPress fork. It may turn out that the fork won’t be necessary after all, but at least the option will be available.