Joomla vs Drupal
Bert Boerland, Drupaleer and employee at Dutch Open Projects, an Open Source implementor in the Netherlands has kindly invited us to take part in the Joomla/Drupal camp they are planning for this summer. Bert explains the concept for the bootcamp on his blog as follows :
Last night I gave a talk on the value of the content management system (CMS) at the Princeton Public Library. Most of it was live demos of Drupal, Joomla and the Jenkins Law Library intranet (a homegrown CMS), but I also had a few intro slides that are now on my Publications & Presentations page
 Gábor Hojtsy shares his insights from comparing several open source CMSs, including Joomla!, Drupal, Plone andTypo3 specific to multilingual support... So which one is the best? "...while generic database overlays are marketed as the most versatile solution, they are very unfriendly and limited for the end users.
Drupal
Source: Drupal statistics at Ohloh.
Hot off the gossip wire: IBM is falling for Drupal. Hmmmm. ECM leader IBM has developed a series of nine tutorials for Open Source CMS Drupal. And as it turns out, Drupal runs rather well on IBM Linux servers while plugged-into IBM’s DB2 Express-C database. The final tutorial covers just exactly how to do that. The IBM team compared several popular products including Mambo, Typo3, Ruby on Rails, Movable Type, WordPress, and TextPattern before selecting Drupal.
I originally wrote this article for the Xaneon Development site way back in August 2005. After Xaneon shut down and this article became unavailable, a number of people e-mailed me to ask for it, so I dug up my local copy and decided to publish it here. Note that since this was written, Mambo has become Joomla and both Drupal and Joomla have evolved and come out with new releases. Nevertheless, for what it’s worth, here follows the article in its original form.
Since our announcement regarding the impending demise of XE2, we’ve received a ton of e-mail from people asking us to elaborate on the reasons we decided to “defect” from Mambo to Drupal. Instead of answering this question over and over, we’ve decided to publish a brief (well, that was the intention, anyway…) overview of what has led us to, ultimately, abandon Mambo.
The OSInet team recently attended Solutions Linux, a trade fair focused on FLOSS, and while chatting with a sales engineer from a company specialized in Typo3, got asked which CMS we used, and of course answered "Drupal".
Recently I have gotten quite a few questions about why we chose to move stmarkdc.org from Joomla! to Drupal. Our main motivators were Drupal’s taxonomy system that allows for tagging with granular access control (allows a ministry to update only their section and nothing else) and polished multi-lingual support. Drupal is a little more complex to get up and running but for sites with a lot of content the flexibility is great.
When it came time to update LAF's public website and Intranet, it was my job to figure out the tech behind the site. I was bound and determined to move LAF into the new millenium, put us on a web content management system (CMS), and move the task of updating the sites from one tech staff person to the hands of a few. I needed a well supported, easy to use, modular, and flexible system. Oh yeah, and it needed to be free.
John Galvin of io1 describes the process his company went through in transitioning from their own XML/XSL content management development to Drupal. After looking at Joomla! and other PHP-based CMS solutions, they settled on Drupal in large part because if its strength with handling taxonomies. Copyright © 2008 GLORilla.com All Rights Reserved. |
 |
|
|
|
|
|
 |
Except where otherwise noted, content on this site is
licensed under
a Creative Commons Attribution 3.0 License |
Powered by GLORilla.com |