Lee's Weblog

Anyone who has worked with me can testify – somewhat to my dismay – that my CMS of choice is Drupal, not WordPress. So why am I using wordpress when I could blog in Drupal…? Ever hear the phrase, “right tool for the job?” Well, this is it for blogging.

Drupal is great at what it does…I suppose. The problem is that you can never really define what Drupal actually does without both short-changing and overstating its capabilities. The concept behind a fully generic CMS is GREAT! This means that I can arbitrarily add data, create different types of data, and so on…and Drupal allows for this! So what, then, is the problem?

The problem is … who wants to mess with code just to set up a blog? Who wants to download 38 different access control modules to find the one you’re comfortable with? Who wants partially implemented and partially working modules? No one! As a self-proclaimed Drupal Ninja, I can tell you the shortcomming: A lack of a strong identity with a robust integrated featureset. That’s not to say that Drupal core isnt stable and robust…but for WHAT PURPOSE?

So we go back to the previous question…what is Drupal? Is it a Weblog? No. Is it a Program management/Groupware suite? No. Is it a tool for document management? No. Could it be ALL THE ABOVE AND MORE? CERTIANLY! But that costs time and money…

Long story short…I make a living off of developing and “selling” Drupal sites…and when I wanted a Blog, I chose a Blog package: WordPress.  Some food for thought.