Not too long ago, I interviewed Jeff Robbins, CEO of Lullabot about Drupal, and the powerful websites being built with it. Since then, Communicate.io, my marketing agency now into year 10, has become partners with Lullabot to utilize and find expertise for our own customers suited for Drupal integrations. Many agencies and web developers choose to support either one or the other, Drupal, or it’s commonly associated competitor, Joomla. We happen to do both, seeing their individual strengths and staying flexible for our clients. Having a difficult time choosing? Here are some recent reasons for using either.
On Communicopia’s blog, a discussion started recently for beginners about these two platforms:
I added my own commentary here: http://www.communicopia.com/blog/joomla-versus-drupal#comment-9435
Submitted by Lisa Padilla (not verified) on June 25, 2010 – 1:04pm.
Apples and oranges/pears/pineapples, whatever you want to call it, Joomla and Drupal each have different structures and expansion requirements. I think it depends on which add-ons/modules/additional functionality are required for the website.
Some Joomla suites of software are just the right thing. If something essential is missing and a client must stay on Joomla, a CSS specialist is needed, not just someone who can figure out Joomla. Once the CSS is tight, a relatively technical marketing resource could realistically manage the site.
I have seen Drupal stop companies in their tracks once they realize they can’t figure it out with their existing IT, or worse yet marketing, team. So, you hire an (expensive) Drupal specialist who brings you up-to-date, but then need to rely on them to upgrade or implement a new module.
The scaling issue is mostly about hosting the content of the site and making requests for information to a server (hopefully in the cloud, where all of our heads should be by now). That server however, could reside underneath your friend Neal’s desk somewhere, but with a cloud partner like Amazon you have technical support, tiered expansion and costs and let’s face it, Neal sleeps.”
By writing a full-featured description of your desired website functionality before getting started, and assess the skills of your internal team before starting with either.