[Post originally published on May 8, 2017. Updated on February 26, 2019.]
Official rant: WordPress’ basic approach is backwards from what old school (1990’s, HTML) folks, like me, expect to see.
I want to start with a structure and then fill it in with content. WordPress seems to think that I want to start with the content and then create the structure around it. Huh? That is like saying that, when you build a new home, you place your belongings on the dirt of the empty lot and then frame the house around your belongings.
Don’t dis’ my analogy! It’s spot on! 😉
I want someone else to make the structure and to make it pretty. I want to take that pretty structure and fill it in with my useful content.
What I did at first, when I first started playing with WordPress in 2017, was what I thought I was supposed to do. I searched the web for a beautiful and appealing WordPress theme. I found one. I looked at the demo page. It was beautiful, with the menu bar I wanted and the pages I wanted. Excellent! Then I installed it…
Where did the pages, menu bar, and images go? Poof! I had to create them myself, from scratch, to re-invent what I saw in the demo.
What? I could have just downloaded a good-looking, responsive, HTML5-compliant website template, replaced the graphics and text with mine, and badda-boom, badda-bing, I would have been in business.
It must be the SEO aspect of WordPress that is the attraction. Certainly I could run a blog without installing WordPress, learning PHP, managing an SQL database, figuring out the difference between “tools”, “settings”, “appearance”, “plugins”, and “widgets”, et cetera. (Ah, Grasshopper. Is it a “plugin” or a “widget”? We must unpack this…)
How about the “custom HTML” feature of WordPress? Custom HTML? Seriously? I thought you were trying to protect me from mean old HTML! 😉
Being an old school, guy, I would just have a static HTML web page. I would edit it. I would add a new paragraph and maybe an image. I would save the file. Done. Blog updated.