Today’s the official launch of my redesigned blog!
I’ve spent the past week or so migrating my site from a Drupal (v.5) platform to a WordPress (v.2.7) one. And after a lot of experimental SQL scripts, I’m finally done. If you hopped on my site late last night, you were greeted with an “Undergoing Maintenance” message, until I pushed the new site live early this morning before coming to work (I was too excited to even wait for my first cup of coffee).
I am a big fan of Drupal. For “real” sites that require a “real” content management system that allows for scalability and lots of bells and whistles, Drupal can’t be beat. Which is why I love Drupal so much. I’ve used it to develop an intranet for my show chorus and a website for my church. The amount of work it takes to develop in Drupal scores a big payoff for sites like those.
But my site is just a blog with a few static pages. And as much as I love the challenge of building with Drupal, it just can’t compare to WordPress for blogging, and it takes a lot of configuration to add new plugins (modules in Drupal talk). I don’t mind that work for more complex sites, but it’s a bit of overkill for a simple blog site like mine. And lately, I’ve found myself spending much of my free time making coding changes instead of having time to actually blog and produce content. So, I opted to make the move and migrate my site back to WordPress (I used a much earlier version of WordPress in my site’s first life).
I used to develop in WordPress years ago, but grew frustrated with the limited ability to customize the site architecture, without hard-coding into the template, and with the laborious process required to install and configure plugins (much like the amount of work it takes to install and configure Drupal modules).
But when I launched our food blog a couple months ago, I opted to go with WordPress for the same reasons I am making the switch now for my own site. I also develop on WordPress at work now, too, so I’ve had time and cause to grow very fond of the WordPress blogging platform this time around. I will still develop with Drupal, especially for more complex sites, but I plan to stick with WordPress for basic blogging sites — including mine.
Oh, and just in case you’re wondering… I opted to stay with v.2.7 instead of upgrading to v.2.8 because I wasn’t sure if all the themes and plugins I like have been ported to v.2.8 yet. Once I have the time to get familiar with 2.8, and assess if my theme and plugins are compatible, I will probably push the site to 2.8.
Note: My apologies to my blog subscribers. The migration of all my blog posts into the new database will probably cause your blog readers to suddenly populate with a bunch of “new” old blog posts. That was the one obstacle I just couldn’t fix or avoid.