I'm going to be doing a talk in a couple of weeks called "10 reasons why Drupal (might) kick your CMS's a**" to a local group of web tech folks, only a couple of which use Drupal. I have some ideas, but wanted to crowdsource this a bit and see if I can get some input from the community. I have a very limited exposure to other popular CMS's, so any input on comparing and contrasting Jooma, Wordpress and Drupal would be appreciated. Also, any nifty graphs or diagrams that might hit the points home? So far, here are some items on my list:
- Caching - The various caching tools enable Drupal to perform nearly as fast as static HTML
- Community - Lots of IRC participation, local user groups, positive leadership
- No forking - The community hasn't yet reached the point where a schism caused forking.
- Central module repository - This has meant that all projects are supported in similar ways (version control, issue queues, etc) and that they are GPL compliant. Also, this adds exposure for the modules and they get vetted by the community.
- Drupal is a programming framework plus a CMS - Drupal does a lot of heavy lifting, and helps you organize your code in a meaningful way other folks can plg into.
- Drupal modules don't have to hack core to work - As opposed to other CMSs
- Drupal scales well - And this will only get better with Drupal 7 and the new database layer
- Drupal is mature - It's been around a while, it's stable and is being supported by a lot of big projects (need some good diagrams here)
- Extendable data structures (i.e. fields in core) - Makes all data flexible at the interface level
I'd love to have some good visuals for this, and I'd also like to get some ideas on what I might be missing. I will gladly open source this presentation as well once it's complete.