behind AotW

When it rains, it pours goes the old saw. For the last couple of weeks I’ve been up to my ear lobes in two proposal writing projects. I expect two more by the end of March. The normal pace is two in a year. These are good for business, but hard on my personal and online lives.

This time crunch has tightly focused the effort I told you about in a December post about an off-the-shelf content management system (CMS) as basis for a website. To recap: I’m working a pro bono project to help a worthy historical non-profit upgrade their online presence. Last we talked I had built a demo website on WordPress and was planning to migrate to the more sophisticated Textpattern platform.

I just won’t have time for that anytime soon, and the non-profit wants to publish fast. So, after some reassuring research, I’ve decided to stick with WordPress and avoid the learning curve and rework needed to implement on Textpattern.

Why?

First, there is an array of proven plugins and custom modules available for WordPress to meet all the likely business needs of the client. Just ask Lorelle, for instance. Sure, there is danger that too many plugins or widgets will result in Lego architecture, but for the few functions we’re considering, I think the maintenance burden will be low.

Second, the client wants to implement new functions and features iteratively–one at a time at a moderate pace–so I will have opportunity to write custom PHP within the WordPress framework or bite the bullet and convert to a new platform later, if worst comes to worst.

It comes down to the fastest and easiest way to get function online with minimum investment.

I’d appreciate hearing from anyone with similar projects: I need all the advice I can get! I’ll keep you up on how it goes …