Classic Editor makes it super easy to build websites in WordPress
-
I have been developing in WordPress for almost 13 years and I love the way that it was organized. Easy access to customize CSS, widgets, menus, functions.php, templating, etc.
Losing these tools means I have to fight with Gutenberg, one of the worst UIs I’ve ever had to deal with. It’s pretty, but horrible. This critique is from someone who is primarily a graphic designer with mad web skills. It’s NOT good design. You have to guess so much. I was trying to simply change a permalink on a page the other day. It took me 20 minutes and massive online research to figure out that clicking on the page link opens up the permalink editor! Why can’t you just label things properly? Oh, that’s right. It would ruin your design.
Design that hides function is BAD design. Okay? Design 101, already. Gutenberg reduces my productivity by at least 50%, which means I either have to pass these costs to my clients or work for free to stay competitive.
My biggest gripe is the choice to hide the custom CSS editor. I use custom CSS all the time to overcome theming limitations. I don’t want to work in an editor that is 250px wide, thanks. I need a full-width, page-sized editor so I can actually see my custom code. And, now I hear that they’ve completely done away with allowing any global CSS editing at all. You can only apply styles to blocks. Just ridiculous.
I am never going to build a WordPress site where I don’t code CSS and custom PHP. FSE is for the birds. I need to code. I will work around this inefficient set up for as long as I can. If WordPress decides to sunset the ability to code, to use the classic editor, to use alternative page builders permanently – I will find a new platform. I won’t be forced to use inefficient tools that don’t serve me as a developer.
My 2 cents.
- The topic ‘Classic Editor makes it super easy to build websites in WordPress’ is closed to new replies.