Drupal vs. the Others


Published on

Comparison of Drupal against other systems Exove is using -- WordPress, Joomla!, eZ Publish, and CodeIgniter

Published in: Technology
1 Comment
  • Nice presentation.
    Ref slide 19 : 'Open source version not released officially anymore' : This is wrong. The eZ Publish Community Project is available, and built every month. The latest build to date is :

    Staying tuned on the activity on the open-source side can be done through following this blog : http://share.ez.no/blogs/community-project-board (RSS available here : http://share.ez.no/get-involved/exchange#RSS )
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Drupal vs. the Others

  1. 1. Drupal vs. the Others<br />DrupalCampStockholmMay 6, 2011<br />Janne KalliolaKalleVarisvirta<br />
  2. 2. Agenda<br />A couple of words about Exove<br />Systems<br />WordPress<br />eZ Publish<br />Joomla!<br />CodeIgniter<br />Drupal<br />Positioning<br />
  3. 3. Exove enables companies to conduct better business on the Internetthrough best-of-breed personnel and solutions<br />
  4. 4. We design and implement beautiful, functional, and business-driven solutions<br />
  5. 5. Company in a nutshell<br />We specialise in designing and developing sites, web applications, mobile apps, and community platforms<br />Founded 2006, now employing 46 people<br />Operations in Finland and Estonia, clients all over the place<br />Clients ranging from small start-ups to big media companies, telco operators and multinational corporations<br />Usually Exove chooses the CMS system to build on<br />Mainly focusing on systems created on LAMP (Linux Apache MySQL PHP), due to easy-to-match requirements for hosting<br />
  6. 6. Platforms used by Exove<br />Currently and frequently used<br />Drupal (GPL)<br />eZ Publish (Commercial + GPL)<br />Wordpress (GPL)<br />CodeIgniter (own open source license, permissive)<br />PhoneGAP<br />Previously or from time to time used<br />CMS Made Simple (GPL)<br />Joomla! (GPL)<br />Symfony (MIT)<br />
  7. 7. Systems in this presentation<br />The systems discussed are all used by Exove<br />They do not represent the complete spectrum of available content management systems<br />They have been selected to provide a good coverage for various customer needs<br />All systems are based on LAMP<br />There are excellent systems on other platforms, such as Liferay and DotNetNuke, that could be viable alternatives for the systems in this presentation<br />All systems are open source<br />There are also good closed source systems, but we are not speaking about them now<br />
  8. 8. www.wordpress.org<br />www.wordpress.com<br />Wordpress<br />
  9. 9. Wordpress<br />A CMS focusing on blogs, “an open source blog publishing application”<br />Also available as a service in wordpress.com<br />Has a huge user base, considered one of the market leaders of open source CMS systems by 2010 market survey by Water & Stone <br />www.waterandstone.com/book/2010-open-source-cms-market-share-report<br />Powers around 14% of websites accorgind to W3Techs survey (Apr 28, 2011)<br />w3techs.com/technologies/overview/content_management/all<br />
  10. 10.
  11. 11. Wordpress<br />Focuses on making things easy<br />Administration panel is easy to use<br />The whole system is easy to configure and edit with integrated editors for CSS and template files<br />A plugin architecture for extending the system<br />Recently included proper support for extending content types and multi-sites<br />The leader in both installations and brand exposure<br />
  12. 12. +<br />Easy administration<br />A lot of core features<br />A lot of plugins for extra functionality<br />Huge number of readymade themes<br />Very intuitive API for plugin development, a plugin can be built in 30 minutes<br />Focuses really on blogging, considered one of the best blogging platforms<br />-<br />Still quite blog-driven<br />Plugin quality varies<br />From dirty template hacks to proper full-blown feature-packs with proper settings in admin<br />No proper separation of content and presentation in plugins<br />Performance is really weak without caching<br />Community features are not in main focus<br />Achievable through plugins<br />Wordpress<br />
  13. 13. When do we choose Wordpress<br />When the site is small or medium in size<br />When the site focuses primarily on blogging<br />When the requirements do not specify a lot more features than Wordpress can provide<br />We have implemented some plugins, but extending WP to match one of the fully featured CMSes(like Drupal) would take years<br />When the site does not need a lot of community features<br />
  14. 14. Why would we choose Wordpress (over Drupal)<br />Essentially, makes the site cheaper for clients needing a small or medium site<br />Setup time is faster, whole setting up does not really need any contribution outside HTML developers<br />Very easy and clear administration panel<br />Easy to train, easy to use<br />Small maintenance burden<br />
  15. 15. www.ez.no<br />eZ Publish<br />
  16. 16. eZ Publish<br />Developed by eZ Systems AS (a Norwegian commercial open source company)<br />Smallish community, but complemented nicely by a company<br />All-in-one enterprise content management system<br />Huge feature list<br />Focused on major corporate sites<br />
  17. 17.
  18. 18. eZ Publish<br />Very flexible and powerful content model<br />Integrated workflow and timed publish features<br />Fine-grained administration rights management<br />Very sophisticated multi-site and multi-language support<br />Two ways to administer the site, a toolbar approach along with the traditional administration panel<br />Also able to work as a intranet system<br />
  19. 19. +<br />Easy and yet powerful administration interface<br />Caters for all required corporate features out of the box<br />Excellent search through deep SOLR integration (eZ Find)<br />Sophisticated caching<br />Highly developed administration processes<br />Commercial support available<br />-<br />Community features not that advanced<br />Focus on users enriching the content, not generating it<br />Extending eZ requires a lot of knowledge<br />Only a few dozen extensions<br />On the other hand, the base system takes care of most needs already<br />Open source version not released officially anymore<br />eZ Publish<br />
  20. 20. When do we choose eZ Publish<br />When the site is from big to huge semi-static corporate site<br />When the site needs very sophisticated administration features<br />Typically, non-technical people maintaining the site<br />When the site focuses on top down content (like a newspaper, a magazine, or a corporate site)<br />When customer requires commercial entity behind the system<br />
  21. 21. Why would we choose eZ Publish (over Drupal)<br />More needed functionalities in the core (if the requirements demand a lot)<br />When workflow on administration side is essential and needs strict control on user privileges<br />This can again be achieved with Drupal’s contrib modules, but needs a combination of modules that typically have some compatibility issues<br />Need for multilingual and/or multidomain support<br />The system is fabulous for multi-country deployments<br />
  22. 22. www.joomla.org<br />Joomla!<br />
  23. 23. Joomla!<br />Open source CMS with long history (2000->)<br />Excellent positioning in search engines, community pays focus on marketing<br />Has a huge user base, considered one of the market leaders of open source CMS systems by 2010 market survey by Water & Stone <br />www.waterandstone.com/book/2010-open-source-cms-market-share-report<br />
  24. 24.
  25. 25. Joomla!<br />Simple and powerful content model<br />A lot of extensions for various purposes<br />Based on model-view-controller paradigm<br />Better than usual admin user interface<br />Powerful templating system<br />Very designer friendly, focus on making sites look fantastic with little effort<br />
  26. 26. +<br />Big community<br />A lot of extensions, readymade themes, and such<br />Extensions are easy to install<br />Relatively friendly admin interface<br />-<br />Content model is simple and requires extensions<br />Extensions are hard to build<br />Some internal concepts are confusing<br />Lagging behind compared to WordPress and Drupal<br />Joomla!<br />
  27. 27. When do we choose Joomla!<br />When the customer has selected the system as part of their technology portfolio<br />When WordPress is not enough and Drupal admin UI is too intimidating<br />When site features can be achieved with readymade extensions<br />
  28. 28. Why would we choose Joomla! (over Drupal)<br />We do not see any reason to select Joomla! instead of Drupal or eZ Publish<br />Unless there are non-CMS reasons, such as technology portfolio selection<br />However, Joomla! has very good traction especially outside Finland<br />The install base is 2-4 bigger compared to Drupal (depends on measurement)<br />
  29. 29. www.codeigniter.com<br />CodeIgniter<br />
  30. 30. CodeIgniter<br />A model-view-controller based PHP framework from EllisLabs<br />Simple, lightweight, and powerful framework for implementing web services and applications<br />Does not contain CMS features<br />There are content management systems built on top of CodeIgniter, but we have not used them<br />Semiactive community<br />
  31. 31.
  32. 32. CodeIgniter<br />Has really short path to the user’s code<br />Comprehensive support for basic operations<br />Does not force developers to use certain way of doing things (hooks, scaffoldings, XML mappings, etc.)<br />Recently bumped into version 2.0 and broke backwards compatibility<br />We have not yet tried the new version<br />
  33. 33. +<br />Very fast compared to all other systems in this presentation<br />Very simple to learn<br />No need to fight against the system<br />Excellent separation of content and presentation<br />Very good and comprehensive documentation<br />Better open source license for commercial purposes<br />-<br />No CMS<br />We have integrated WordPress with a special bridge<br />The view system allows logic in views<br />We have fixed this with Smarty integration<br />KohanaPHP (former fork, now rewritten) is faster and provides more features<br />The community is smallish<br />CodeIgniter<br />
  34. 34. When do we choose CodeIgniter<br />When there is no or little need for CMS features<br />We have integrated CodeIgniter with WordPress in certain cases<br />When the data model is truly complex and cannot be tackled with predefined database schemas<br />When adding new features to Drupal or eZ Publish would take longer than writing everything from scratch<br />
  35. 35. Why would we choose CodeIgniter (over Drupal)<br />Way faster<br />Faster development time when coding is a must<br />Better separation of content and presentation<br />Allows to use own database schemas as seen fit<br />Also easy to use with SOLR, MongoDB and such<br />
  36. 36. www.drupal.org<br />Drupal<br />
  37. 37. Drupal<br />A fully featured CMS with great community and UGC (user-generated content) support<br />Literally thousands of modules and a very active development community – as you should know<br />Has a huge user base, considered one of the market leaders of open source CMS systems by 2010 market survey by Water & Stone <br />www.waterandstone.com/book/2010-open-source-cms-market-share-report<br />
  38. 38.
  39. 39. Drupal<br />Multi-language and multi-site support in the core<br />Has a great API, a lot of hooks and toolkit overrides for extending<br />Has a decent documentation, even very good if you compare it to other open-source products<br />
  40. 40. +<br />Excellent community feature support<br />Extendible easily and to pretty much anything<br />Widely used<br />Huge user-base<br />Active community, quality contrib modules available<br />Install profiles<br />-<br />Not enough features in the core for typical CMS case<br />Tricky admin interface<br />Caching is somewhat limited<br />No integrated admin workflow with user access controls<br />Community focuses too much on code, marketing seems to be a hindsight<br />Drupal.org is not “selling” the system at all<br />Drupal<br />
  41. 41. When do we choose Drupal 1/2<br />When the client specifically wants it (this is way more common for Drupal than any other CMS - in Finland, your mileage may vary)<br />You can create pretty much any site with Drupal – the other CMSesjust might do some specific sites faster to build or easier to use<br />When the site focuses on community and user generated content<br />There is no match to Drupal’s community features, as we see it<br />
  42. 42. When do we choose Drupal 2/2<br />When the client wants/needs a CMS for which they can get support from a lot of technology companies in Finland (it’s probably the most supported here)<br />When we need the CMS to bend to anything we want<br />There’s no match to Drupal’s API and flexibility for extending on<br />You can build pretty much anything on Drupal, without breaking the core<br />
  43. 43. Positioning<br />
  44. 44. Comparison of the systemsUser perspective<br />User generated<br />Drupal<br />WordPress<br />Joomla!<br />Contet sources<br />Site size<br />Big size<br />Small size<br />eZ Publish<br />Top-down information<br />
  45. 45. Powerful<br />CodeIgniter<br />eZ Publish<br />Drupal<br />API<br />Joomla!<br />Development<br />Easy<br />Hard<br />WordPress<br />Restricted<br />Comparison of the systemsDeveloper perspective<br />
  46. 46. Recap<br />Different systems serve different needs<br />There is no fit-for-all system available<br />Drupal is quite a good candidate for an all-around system<br />
  47. 47. Want to hear more from us?<br />www.exove.com@exove<br />Meet us at Drupal Business Days and Drupal CXO<br />May 25-27 in Helsinki<br />
  48. 48. Questions? Comments?<br />Thank you for your time<br />