Mambo/Joomla vs. Drupal

in

I've done a few projects using Mambo/Joomla and (at the time) was very impressed with this CMS:

  • Easy to theme
  • Great administrative tools
  • Easy to maintain
  • Structured content publishing paradigm (Category/Subject)
  • Easy to learn

I liked Joomla so much I've been using it for my personal website for the past 2 years.

Drupal logoAt work we started evaluating other CMS packages, including Joomla, and using Joomla was my first choice. However my friend and co-worker Cedric suggested we check out Drupal. I'd heard of Drupal before and had visited the site a few times but was initially put off by (what seemed to be) the very unstructured nature of this package. More specificially, perhaps due to my experience with Joomla, Drupal seemed very foreign: I didn't understand the Vocabulary/Taxonomy system for tagging content.

Cedric suggested I read up on Drupal and over Christmas break I installed it and began using the tool. After a few hours all I can say is WOW. Drupal rocks! I was (and am still) blown away by how powerful and well thought-out this package is. We've been using it at work for a big project and Cedric's decision to use this tool has paid dividends several-fold. One of the huge advantages for us was the ability to downloa, install, customize, and use "off the shelf" modules to meet a variety of feature requests from the client. Apart from the dizzying assortment of modules available Drupal's core architecture is well designed, tested, and has well documented hooks and api's that allow web developers to extend and customize the system to the extent that our project doesn't behave like other Drupal powered websites. This is a key advantage and attests to the power and flexibility of the core system.

Currently I'm rebuilding my personal website using Drupal. I'm leveraging much of the knowledge and skills I've aquired from the project at work and am having loads of fun using Drupal. Can't wait till my new website is done.