Hello this is just a discussion i am a Joomla fan
I am trying to do some research into the diffrences between some of the best CMS available ........
Someone said its very difficult to compare CMS since it all depends on you needs
. I did some Googling . Seem there are more negative views and reviews for Mambo(Joomla) from developers than for drupal and postive views and reviews for Mambo(Joomla) from web designers and end users than for drupal
People who support Mambo(Joomla) are mostly attracted due to its user friendlyness and looks. Seems Drupal is more powerful
....... I could be wrong here are a list of things i found Could the Mods and core Developers Clarify if any of my findings were wrongUse Mambo(Joomla) when:
* you don't know about the tech stuff at all
* you want easy install & setup with your mouse
* you don't want to learn the tool you're using
* you don't need to integrate other scripts etc. to your site
* you want a candy site and don't mind several other sites using the same template(s)
* you don't need SEO out of the box
* you don't care about server resources
* you're running (or planning to to run) only one or max a couple of sites
* you don't need one log-in to several sites
* you don't need user groups & permissions
* you don't run membership site(s)Use Drupal when:
* you want a rock solid & high quality platform for your sites
* you want or need a real multi-site-feature (only one installation for several sites)
* you need any kind of user groups & user permissions
* you need to run also membership- and community sites, not only CMS etc
* you want a Powerful templating system
* you're ready to invest a bit of your time in order to realize all the huge possibilities of Drupal
* you understand the meaning of clear, high quality code and API (easy to integrate with other solutions etc)
* you want flexibility and don't like limitationsfor More details go here http://forums.digitalpoint.com/showpost.php?p=257154&postcount=19
From Some Forum i was going troug Drupal is superior in SEO (our Development Team recently changed our future development(s) from Mambo(Joomla) to Drupal - and SEO was just one of the reasons for that)A number of Major Advantages of Drupal over Mambo(Joomla)
With Drupal, you can set up several sites with only one installation ...think about that, when you have tens of sites and security holes are found almost daily! ...what about then, when you quickly need to uppdate some additional components / modules / themes... you actually face a lot of work in Mambo(Joomla) - in Drupal you do it only once.
With Drupal, you can (if you want to) use the same log-in-details for different sites... in some cases it opens quite interesting possibilities.
Drupal has also SEO-friendly URL's out of the box... for Mambo(Joomla), you need to buy a commercial component from a core developer or use labor-intensive free ones.
Someone mentioned, that Drupal is focused on communities... you're right... however, it does not mean, you can't use Drupal for content sites. Actually, Drupal is a great choise also for content sites. I can't imagine Mambo(Joomla) as a natural community building system, though.
When talking about user profiles and permissions to different parts of the site, Mambo(Joomla) is actually a joke... on the other hand, Drupal is the opposite... it's so easy to set up and fine tune different user-roles and give them some permisssions etc... what a power.
The user and administrative interface for Mambo(Joomla) was one of the best-designed options on our shortlist. We were also interested to note the emergence of Soapbox, a Mambo(Joomla) toolset geared towards the nonprofit community. The Soapbox toolset is however limited (at this point) to integration with the Democracy in Action CRM, and to single sign-on among sites. The information architecture of Mambo(Joomla) itself proved incompatible with the telecentre.org project, since it is structured around categorization (rather than tagging), which in practice imposes such limitations as precluding multiple categorization of inbound RSS feeds. Since much of the telecentre.org network’s content will need to be distributed to multiple categories (e.g. a story on a Bolivian wifi project needs to be tagged “wifi” and “Latin America”), the categorization structure was a deal-breaker. For more details go here http://drupal.org/node/28589Drupal:
With a fast-growing user base in the non-profit sector, Drupal’s strong online community focus made it an appealing prospect. Most importantly, Drupal was alone among all CMS options in its compatibility with a distributed network approach. The platform is essentially built for exactly this kind of approach: it supports ubiquitous outbound RSS feeds, complex aggregation of inbound feeds, per-feed or per-item non-exclusive tagging, and native support for blogging. Compared to the other options, which are virtually all CMS platforms that have developed distributed community features, Drupal is innately oriented towards community networking and distributed content creation. The following outlines how we anticipate using particular features of the Drupal platform to support core elements of the telecentre.org web strategy.For more details go here http://drupal.org/node/28590