Building 2.0, part 9: Toolset Handcuffs

One of the big reasons I wanted to put all of the content into WordPress was because I’d found that I’d begun putting almost everything into the blog rather than other areas of the site. It wasn’t a conscious decision, it was just so much easier to update the blog than the other pages in the site.

This shift was a bit of a practical problem because there are other areas of my site that need updating on a regular basis. For example, my various project pages that need updating on each release, etc. At times I would actually delay releasing something that was done and ready just because I didn’t have time or easy SFTP access.

As I’ve already touched on briefly, the transition of all of the site content into the WordPress database gave me a number of benefits (more on this in the next installment), one of the big benefits was the ability to easily update the site from a web interface.

That wasn’t the only change I made though, I finally did for what I’d done for a while ago, put the entire site in SVN. This makes it easy for me to test local changes and push them to the site as well as push changes I make live on the site back into a local test environment. It also means that the site is backed up to S3 along with the rest of my SVN repositories.

These may sound like small changes, but they are fundamental to the way I manage this site. If you’re finding yourself reluctant to make changes on one of your web sites, ask yourself: Self, is your web site maintenance toolset holding you back?