Content Management

I adore the simplicity of the design, but even better, I like the sentiment of that post.

I’d love to find another, more workable platform. Or better way to do it. As it is, though, I’ve streamlined the processes as much as I can, for the time being; and, times being what they are. I probably spend too much time tweaking the page output, still, and I refuse to always consider it procrastination. To be fair, sometimes it is.

I’ve used a couple of the mentioned blog motors, as I prefer to think about them since the term Content Management Software/System seems dry and too sterile.

For several years, I rolled my own content management. Why I switched to WordPress after thoroughly road-testing it — with stops along the way for Grey Matter and Expression Engine, which might explain why I prefer the term, “blog motor.”

That’s an impressive laundry list of what’s wanted for a motor. The biggest problem with WordPress is that it works, and it’s also like a Swiss Army Knife, only, it’s able to be customized.

The problem is overhead, processor time. “Bandwidth.” It’s why I’m no longer on a server, but back at a server farm. Which, I might add, I like, since there’s more than adequate processor cycles included to make a couple of installations of WordPress run without over-cooking the hardware.

For all the heavyweight hosting needs:

I’m always open to ideas. I’d like to find something that requires nothing more than a web browser and access for all the management.

New motors that use less horsepower. The car analogy won’t die, just yet. Last time, in the car dealership, was it about horsepower under the hood, what kind motor it was, carbs or fuel injection? Or how to use the bluetooth on the steering wheel?

Software, the backend — the business end where I spend time — like it faster and smoother.

As it is? This almost falls in a “hobbyist” kind of category.