Download our free how-to guide for setting up your new Drupal site and using our themes

Drupal vs. Joomla: a frank comparison from an IBM consultant

We were very fortunate recently to have a consultant from IBM purchase one of our Drupal themes for a personal project. Before purchasing the theme, we discussed a bit about Joomla and Drupal, focusing mostly on the difference between where functionality and eye candy lies in Drupal vs. Joomla.

I say fortunate because after this consultant evaluated the two CMSes, I received an email with a fascinating and detailed comparison of these early experiences with Drupal and Joomla. I was allowed to post this (anonymously) here to our blog so the community(ies) at large can benefit from this great write-up.

I won’t interject too much of my own thoughts here, other than that a) I agree with just about everything being said here, and b) the good news is that a ton of this stuff is a strong focus for Drupal 7. I see the Drupal community also putting more effort into the many approaches currently being worked on for pre-configuring/populating a site (Installation profiles, Patterns, Spaces, Drush, etc).

Edit: we’re getting some very interesting comments from Joomla users as well, make sure you read the comments!

The full email follows below

FYI, here are my observations on Drupal after about 40-50 hours with the tool (I have experience with Joomla, DotNetNuke, and of course our solution at IBM: Websphere Portal, WCM, and Portlet Factory). I plan to evaluate for another few days, before making a decision on whether to implement using Joomla or Drupal.  The hosting costs and portlet dev cost for Websphere Portal are too high, or I’d be using an IBM solution.

Drupal vs. Joomla

Site Building
- Flexibility & Power: Drupal looks significantly more powerful — much more flexible.  Looks like Views, CCK, Panels give Drupal a huge advantage over Joomla. You simply can’t get that flexibility with Joomla.  Joomla developers design around their own paradigm with very little flexibility. You can get up and running much quicker with Joomla, but you will hit the wall sooner or later.

Performance
- In my initial tests, Drupal blows away Joomla.  With the new version of Joomla, the good template makers junk them up with gee-whiz gadgets that are not suitable for the enterprise

Learning Curve
- Joomla is far easier to get up and running.  Even with all the free videos, blogs, etc, Drupal is still a lot more challenging. Big oppty for comprehensive business business/enterprise book/education

Templates
Joomla wins by a huge margin. For example, companies like Joomlart, Joomlashack do a good job.  Drupal theme companies are simply horrific. What’s needed is a Template strategy that emulates the requirements for the top web sites in the country and, bundles modules, blocks etc. that work out-of-the-box to give businesses a head-start. For example, with our Websphere Portal product, we deliver incredible Themes/Skins that are rock solid and professional with no fuss or muss. I think you guys have a good stated strategy, but you’re missing a big oppty to deliver what enterprises really need. 

Your templates are the best I’ve seen, but, an enterprise that is just getting started with Drupal will still have a huge ramp to climb to get a News site, mag site, etc. to look good.  Joomlart delivers their Teline II template with a special install that gives you all the sample data, all the components in place — everything in place. 

Finally, the biggest problem with Drupal templates is that the developers completely miss one of the key elements that any evaluator looks at: the menu system.  If you don’t have a professional navigation system on your web site, you’re perceived as a low quality site. The other top items: Layout, Graphics, speed are also critical, and Drupal developers don’t seem to care. Exception:

Code developers
Based on my limited review, it looks Drupal coders are much more professional, skilled, disciplined. Good Joomla coders are rare. Must have something to due with the Drupal culture.  I’m sure the Joomla devs are just as capable, they just don’t institute the same rigor

Admin
Drupal’s backend admin functionality is bad. The front end, backend separation is tenuous and confusing. Joomla is far better.

Content Management
- Drupal’s taxonomy system is excellent. Joomla’s "straight-jacket" approach (Content items confined to one Section/Category) is poor. Joomla’s admin console is much easier to organize, find content. Joomla’s WYSIWYGPro is better than the options available for Drupal.

Content Presentation
- Drupal’s tools are very, very good — they don’t come close to the built-in power of IBM tools — but they’re light years better than Joomla. I like CCK, Views, but wonder why they aren’t part of the code base. Seems odd.  WIth Joomla, you have to acquire components that will meet 60-80% of your needs.  For example, iJoomla has a tremendous news component, but it will never meet the capabilities of Drupal’s CCK, Views, etc.

Multitier Deployment
I’m shocked that there are no good tutorials, articles, education on the proper method for implementing Dev, Test, Staging, Dev environments. Drupal and Joomla communities both suffer from this.  Also, basic backup and restore is not addressed adequately.  The Drupal community is clueless on this.  Joomla at least has two good solutions. If I decide to recommend Drupal for a production site, I’l recommend use Xcloner from Joomlaplug — this product will work with Drupal and does backup and restore of the site and the SQL db.

Summary to Date

- Use Joomla if you want to get nice looking site up quickly and can deal with a slower system, rigid content categorization and limited design/configuration options.
- Use Drupal if you want high performance, scalability, good content management and significant design flexibility. But, be prepared to spend a lot of time/money to get the site to look professional.

 

As to themes, I can assure you that wordpress has the best looking contributed themes, and guess what, not only blogging...

I agree with most of that, my primary problem with Drupal being the admin / frontend is not split - this is VERY confusing, I don't care how you argue.

Template support for Drupal is also dire, and when you want to get a head start in a project this is fundamental.

"I care too much about the quality and performance of the complex custom sites I deliver to my clients"
Can we see an example or two of these complex custom sites?

The lack of nested replies in this site "TopNotchThemes.com" is crap. Just as confusing as Drupals admin.

On another note. If you work for a company/client that allows you to fart around forever developing, and paying for it.

then Bjorn's comment applies
"A higher level of complexity is unavoidable and necessary. (If you have a vision for your enterprise-level site, and you don't want to compromise, you need to accept that it will take time and hard work.)"

Craigslist doesn't even use a css file, and has very simple code running it and it rules the universe because Craig Newmark was thinking of actually getting something done instead of Mentally masterbating over his own greatness.

I think the Drupalers are like the early Linux advocates or early website graphic designers... more interested in showing off some superior skill and making projects go on and on. Basically ignoring the end purpose for the tool.

Anyone with enough money for a Drupal coder to build a huge enterprise system would probably be better off going with a Micro$oft solution etc...

The whole point of an open source CMS or CMF(??whatever) is so that anyone can run with it. Not just elite programmers(Like some people posting here claiming they are "Professional Coders" and not Paste and Cutters??? Why re-invent the wheel!! Why pay a "Professional Coder" to create another Newsletter module etc...

CMS like Joomla follows more logical common sense and is why it has the worlds largest community by miles.
Keep It Simple Stupid

Snap out of it!
over and out - geeks

@Get To The Point Already!

May I refer you to this stylesheet from Craigslist>?

I'm not sure you made your point very well. From my experience (have used both quite a bit, but settled on Drupal), Drupal is the one with fewer frills and more flexibility. My results with Joomla! at times were prettier than Drupal, but never more robust.

I should have said it doesn't even look like Craigslist uses a style sheet.
My bad. I was just riffin. Of course they use a style sheet.

My Craigslist comment actually supports drupals lack of theme development.

My point was more about the elitism attitude of some web developers usually on the drupal side. This gives people who are new to the CMS community a mis-direction.

To anyone deciding on either, try them both out for yourself.
They both are easy to learn.

And never mind everyone else' opinions.
Especially mine!

See Ya! Geeks

Nice article, and the bias toward Websphere is good for a laugh. Websphere is the wonderful combination of complex, slow, and expensive that users LOVE to hate :-)

I just started my first Drupal site (ubercart store) a couple of days ago, and the hardest part was understanding that it's NOT a CMS. I have tried all the nukes, and Joombla, and Wordpress, and a bunch of others. They are great for what they do, but none of them can compare to Drupal as an extensible content platform.

The issue that I have with Drupal is similar to the other people here that mentioned the lack of separation between the user interface and admin. I think my solution would be acceptable to both sides of the argument, though :-)

Assign users a default role, but allow users with multiple roles the ability to select their role via a dropdown. Then tie the presentation components (theme, layout, function display, etc.) to each role.

The base install would then install the "user" presentation for anon and authed users, and the "admin" presentation for admins. For people wanting a consistent presentation across all users, they would just need to change the admin theme to the same as the user theme.

I have spent too many hours in the past couple of days struggling with making the admin interface look the way I want without impacting the user interface.

Often comparisons of content management systems are based solely on personal opinion. So I'm trying to get input from Drupal; and/or Joomla users about what they think each system does well and what it doesn't do so well. I am conducting a survey comparing Drupal and Joomla.

I think the survey will facilitate a more methodical examination of the strengths and weaknesses of each system. My goal is to quantify the tradeoffs involved in selecting a CMS.

I'm a fairly well experienced LAMP developer but I've never used Joomla or Drupal (I've used several other CMS and CMF).

Can someone explain to me why people are saying Joomla is limited (why they 'hit the wall' of what it can do)? What, specifically, couldn't Joomla do that Drupal could?

I guess a second question is, if I'm going to build a very specific type of CRM, but I want to have pre-built elements such as calendars, email, reports, etc., is one product better then the other?

Thanks! And thanks for the article and comments - all very informative!

Interesting article. I have been trying to work out whether to use WordPress, Joomla or Drupal for my sites. My latest blog is in WordPress and it works really well, after adding in a number of plugins. But in trying to make a different type of site with WordPress, which many claim is easy to do, I was frustrated and am now trying Joomla and will also try Drupal. My approach is to try for a day or two with each, and with a little knowledge and see how far I get just using my software experience. Then I will pick one and really learn how to use it properly. I know if I spent a few weeks at least on each CMS I could do lots but don't have that time at the moment so am trying my simple, though ugly, test approach. It is giving interesting results.

But back to Drupal, I think it is clear each CMS has its strengths. But trying to work out which is best is like asking which language is better: C++, Python or PHP? The answer is of course they are all excellent at different things.

I know in my case with limited time available, I am trying to devote my efforts to just one CMS and not have to learn all three, but I may have to give up on that and settle on at least two of them, or maybe all three. One article I read somewhere suggested that the best combination for many sites was Joomla, with a WordPress Blog on the side to help with SEO - that might well be the best for most sites. But for the greatest flexibility the clear view seems to be Drupal, but with a steep learning curve. No one seems to talk much about Plone, though. Unfortunately, or perhaps fortunately, there is no one tool (ring) to rule them all :-)

I will continue my research for what to use for my own sites and will try Drupal next week. Then make the call - is it Joomla or is it going to be Drupal?

Thanks again for the article

Owen McNamara

Regarding the post stating that a CMS is for users that want to avoid depending on a developer. A CMS per se is not required to be like that. A Joomla-like CMS chose this path. Drupal chose another. If every CMS out there is going to cater to user-level of professionalism, who's going to provide the flexibility and power? You can't build a powerful web application without knowing what you're building on. There's still a need for a "CMS for pro developers" and Drupal successfully fills that niche.

Jeff,
Here's a scenario of what I think Joomla won't be able to do (correct me if I'm wrong).

You create several custom content types, using CCK and provide field validation rules with appropriate field type templates (there are plenty of modules providing different CCK field types). Then you set fine-grained access permissions not only to the objects represented by these content types, but also separate access permissions for each field that constitutes this object. Thus, you can have a situation where a User-A can create an object "Invoice", but not change other users' invoices, a User-B that cannot change anything in the existing other user's invoice, besides one field - "status" (this user performs workflow control) and a User-C that cannot create or edit any of these, but has the permission to delete the invoice.

In terms of real-life this scenario may not make perfect sense, but it's mean merely to illustrate the level of flexibility you can get with Drupal.

Also, given Joomla's limited categorizing functionality, I don't think you can implement a complex document workflow path/policy based, again, on user roles.

Those are my two cents.

This lays it out best about drupal...(its the module/repository system is far superior as well.)

http://drupal.org/getting-started/before/overview

Nodes = winner!