Astute readers know (or can probably guess) that the software running my various blogs isn’t your standard blog software; in fact, it’s all PHP code that I wrote myself, and have gradually refined over the years.
Truth be told, though, I’m getting sick of it and I’m considering switch everything over to WordPress. Why? Here are some of my reasons:
- My own software is horribly out of date. It might have been cutting edge three or four years ago, but I just haven’t had time to keep up with the Joneses, as it were.
- To that end, I’m just one person with limited time; I can’t compete with an internet-wide community of open source developers contributing to the most popular free blogging platform around.
- The latest version, 2.7, is a major update and it’s really solid—and has all the administrative features I’d want in my own software anyway.
- It’s just time to get with the program.
Needless to say, I have a number of pros and cons as I’m thinking about this.
Pros:
- WordPress is PHP/MySQL, which is what I do. I’m enormously comfortable with it.
- I can still develop blogging tools in PHP in my spare time—just develop/release them for WordPress as plugins.
- My blogging will be much more efficient—one of the problems now is the admin tools on my current software are quirky—essentially I’m spending more effort managing data rather than writing.
- Automatic upgrades to the software (see the "community of open source developers" reason above).
- Ajax-y auto saving of blog posts—this is huge. I don’t have it in my homegrown software, and I’ve lost more than one post and cursed myself for not having an autosave feature.
- There are tons and tons of neat plugins that I’d love to have instant access to, which I would with WordPress. (Trying to get rid of my own "not invented here" attitude.)
Cons:
- It’s going to be a huge pain to migrate all the blogging data from my database tables to the WordPress tables. I have it all backed up, of course, but mapping from one schema to another is work.
- To that end, I may end up losing URL/path info (hello 404 errors!), tagging data, and years’ worth of other massaged data formatting or content. (The major stuff will be fine, of course.)
- Time to do and fix all of those issues, of course. As in, I don’t have that much time at hand.
- Image handling; I know WP likes to put everything under its "wp-content" directory, but I prefer storing images in an "images" directory. I don’t want to move them, and I’m unsure how configurable WP is in regards to it.
I’m thinking it’s going to happen, regardless. And no, I’m not considering any other blogging platforms; WordPress is the only one in consideration.