Classic Editor for Pages
Whenever possible, I use the Classic Editor for all pages. I prefer its semi-WYSIWYG “Visual” interface and, when I want to get cute or at least see what is going on under the hood, I can switch to the “Code” tab to get at the html.
In my experience, using the visual mode and interface of the classic editor is easier for more casual editors.
However, the Classic Editor is not nirvana. It tries to take care of you too much for my taste, and its interaction with the theme adds another layer of interference with me doing what I want to do (the curse of knowing how it could be done). I change the html; it often revises my changes. So, I try another html approach. Eventually, I either figure out what the editor will accept, or I surrender. But you can do just fine as a webmaster without ever futzing with html or CSS.
And if you prefer the Block Editor for your pages, mazel tov.
Block Editor for Posts, and Pages with Javascript
The original Classic Editor is now considered the legacy editor in WPland. The so-called improvement is the Block Editor, a.k.a. Gutenberg (although no one asked Johannes, who lived over 500 years ago, if he would lend his name to it).
The Block Editor is neither WYSIWYG nor a good old text editor for html. And I find the interface to be enigmatic; it takes minimalism to an extreme. That said, if it were my only available tool, I would probably become comfortable with, and perhaps even fond of it as I learned it use it well.
Regardless, for me, the Block Editor has two use cases:
I have found, much to my surprise, that for the way we use posts on our website, using blocks makes them easier to author and edit. (The same cannot be said for posts on a plain old blog, as opposed to posts used within the framework of a website, which is why this blog is on Blogger instead of WordPress.)
