In February of this year, I switched this blog from WordPress to Drupal, the reasons for which are [explained here](/2008/02/08/wordpress-drupal-weblog-migration/). Today, a handful of months later, I’m switching it back.
While Drupal is an amazing platform for software development—indeed, my own company extensively uses Drupal in some our projects—my opinion is that it’s not appropriate for mainstream bloggers.
So, here’s the short tale of my road from WordPress to Drupal, and back again:
* It began ominously, as it took a [software wizard](http://bendiken.net) nearly 10 hours to migrate my WordPress blog to Drupal. One would think that if Drupal were targeting the mainstream, the migration process from the leading platform would be as simple and painless as the process of migrating from, say, Movable Type to WordPress (which I did myself a couple of years ago—done and dusted in about 30 minutes.)
* Not being very happy with the default theme, my first task was to get that improved. Long story short: Drupal theming isn’t for the technical novice. I can hack my way around WordPress theming fairly easily, but couldn’t even find the Drupal theming. When I finally did, I took one look and decided the default theme wasn’t so bad after all.
* One of my first questions was, “So how do I get an email when somebody posts a comment?”. Turns out, that’s not built in. Well, it sort of is, as the capability to *build* that functionality yourself is built in. (You need to define, create and configure some *triggers* and *actions*.)
* My next question was, “Can the email contain a link to directly approve the comment?” Turns out that capability isn’t included either, so our software wizard programmed a new action to include a link to the “Comment Moderation” screen, where I can “publish” a given comment.
* Later, when I had several comments (including some spam) to moderate, I ran into some serious usability issues, the nature of which surprised me given that Drupal is currently on version *six*. It was suggested that I go directly to the Drupal community with a description of these moderation usability issues, and so I did. You can [read my post here](/deadlink), as well as the response, which itself, punctuates the reason I’m switching back to WordPress.
“afandyag” replied, in an uncapitalized, unpunctuated, unhelpful, poorly formed sentence, that I can “*use views to display your desired approval queue comment to read the comment*”. Huh?
It turns out, while *views* is a commonly used word in the English language, and which can mean many things, it also _happens_ to be the term used to refer to a particular element of the Drupal content management system used to generate screens. I happened to know that from our company’s work with Drupal, but I’d hate to think of the poor chap new to Drupal and trying to get some help.
But don’t get me wrong. I’m not at all faulting the Drupal community. I’ve just concluded that mainstream (non-technical) bloggers likeme aren’t the audience that the Drupal community are targeting anyway—a view which is consistent with both my experience and discussions with others (including some of the Drupal module developers.)