Building A Better Web Platform Chart

Building a Better Web Platform – Web Software – Part 4

If you’ve been following us up to this point, you may already have the spoilers as to which Content Management System we decided was the best for us. So with that in mind, let’s address something. When architecting or planning a solution, it is important to keep the big picture in mind. Working from the bottom straight down or the top straight up is a good way to lose focus.

Big Picture Planning

Before we dive into discussing our web software choices, I want to take a moment and go over what our big picture design process looks like. Perhaps you should brace yourself, as our methods are not exactly orthodox, but they do work well for us.

Step One: Alcohol…

I’ll come out and say it. Our best business meetings happen when inhibitions are gone and attention spans can’t focus on personal agendas. These impromptu spirit  induced… discussions… may take longer than a formal suit-and-tie standing meeting at the office, but the ideas and concepts presented are more heartfelt and truer to the nature of those involved. When you can lay everything else aside and have an uninhibited heart-to-heart discussion about passions and directions, the pieces tend to fall into place.

Step Two: Recover…

We’re not as young as we once were, and recovering from these “meetings” takes some time. Between the pain and regret, there is time to reflect on what was said.

Step Three: Act…

Once all the neurons are firing again, it’s time to get to work and accomplish the goals that were discussed. This shouldn’t be an issue. If the meeting was successful, a direction and plan should have been agreed upon by all involved and the only remaining pieces should be the technical implementations.

Why WordPress?

Our discussion went something like this:

If We could just setup simple WordPress sites for people..

>I HATE WordPress so much! Why don’t we just pick a real platform?

Hey I don’t love it either, but it’s so easy just to do things…

> It’s so slow though…

At this point… my comrade ignores my “technical” argument about slowness and performance and moves on to other points. Having made some valid points about ease of use, mass adoption, themes, plugins, and simplicity… we got distracted by a new arrival, or the taxi, or something shiny… I don’t remember…

My programmer / engineer mind went to work arguing away my zealot hatred of WordPress. The internal reflection went something like this,

>If we could just use WordPress to.. build and maintain the sites.. and then… just serve the static html output.. the performance issues would be resolved… And… Learning to write WordPress Plugins may look good on a resume or to a client later…

And so we set about building the platform. Why aren’t we using Drupal? or Joomla? or PHP-Nuke? …Because, it makes more business sense to us to offer something simpler and perhaps more familiar to our clients.

At the very least.. if the clients later decide they would like to move away from us, finding another WordPress host should be trivial. We don’t want to hold our clients hostage. That’s bad.

Published by

Daniel Widrick

An experienced programmer, software developer, and systems administrator, Daniel Widrick is technophile with a passion for making things work better.

Leave a Reply