Yay!

Well, I am not the only one who detests that new “block” editor that came with the so-called “upgrade” for WordPress (what powers this blog.) I read many rants about it on a forum when I was looking for…

… an answer on how to revert to a previous version, my lovely “old-school” editor that this “old-school” coder prefers.

For those not aware, there are various ways to develop web content. The first and original method was to write computer code using the HTML language (Hypertext Markup Language). Codes in HTML tells the browser how to render what you want to appear. Everything from text, font size and color, images (including size and location), headers, footers, sidebars (such as the by-year with drop-down to by-month archive on this blog’s main page) and more.

When I developed my personal boots and leather website years ago, I began by using an interface built by my ISP that took what I wanted to post and wrote the code around it to make it appear on a web page.

That old rudimentary method of posting web pages was my first introduction to what is now called a “content management system” (CMS). However, my first web pages were constructed oddly and had a funky, weird appearance.

I consulted with a man who mentored me — Bill Choissier (Larry of “hot boots” husband) — and from him, I learned more about “hard-coding” for web pages. While I never would be nearly on Bill’s level of skill, I learned enough such that I was able to migrate bootedman.com to its own domain and evolve into the website that it is today, 11 years later.

I also have to admit that search engines helped a lot, too. When I encountered a problem or had a question about “how to write code to make it do this-or-that,” someone somewhere had the answer. I would experiment and try things out. Not all code changes I tried worked. Some were disasters and “blew up” my website. Thankfully, I always had a backup and was able to restore it to an operating “lightweight” site.

I use the word “lightweight” in that unlike many sophisticated websites these days, I do not invoke lengthy, complicated scripts or other background software programs that gather data and slow down the operation of my site. My website is a static display of images, and lots of internal links. That is all I want it to do. And with 905 pages on it, written the “old way” — that is, all hard-coded — I guess I have learned what to do.

Now… back to the subject of this post.

The kiddies who write the backend code that makes WordPress work decided in their infinite wisdom to change the editor to be more like a content management system, instead of its older “code-like” editing system. I understand, in a way, “code-like” editing and having to remember HTML tags (codes) is daunting to many. They get turned off by having to take time to learn something, so they don’t bother.

However, if I have learned anything about CMS systems, is that while they make preparing web pages faster for the rip-and-publish types (usually young’uns who just want to publish a web page without really caring about how it looks), CMS systems are much more difficult for us “old-school” coders who like precision on web publishing to use.

I am not the only one who feels this way. As I mentioned at the start of this post, other people felt the same way, too. And the good thing about WordPress is that when someone wants to create a functionality, such as the “classic editor,” they can write a “plug-in” — a short piece of software — that when activated, I get my familiar and friendly “old-school” classic editor back. Yay!

I am glad I found that “classic editor” plug-in, because otherwise I was seriously thinking of reverting back to an older version of WordPress, which all experts strongly recommend against.

I am now back in business on this blog. I will blog again about boots, leather, and life again soon.

Life is short: kids who invoke these changes without advance notice or even a preview should get a lump of coal in their Christmas stockings.