Comparisons of existing CMF CMS

dkvk edited this page Sep 14, 2010 · 24 revisions
Clone this wiki locally

Feel free to compare the various features of existing CMF/CMS and the pros and cons of features.

Adobe Business Catalyst

Pros

  • In-context inline editing
  • Built in Web Analytics
  • Built in Web Forms Builder
  • Built in Shopping Cart Capability
  • Built in Email Marketing/Mailing system
  • Built in Reporting Tools
  • Easy to use

Cons

  • Commercial Product
  • Hosted

ModX Revolution

Pros

  • Interface
  • MVC API
  • MVC2
  • Community
  • Documentation

Cons

  • Lack of LDAP/Active Directory/Open Directory Integration

Apostrophe

Pros

  • Symfony-based
  • Open source
  • In-context inline editing
  • Integrated blogging and content reuse
  • Versioning
  • Easy integration with other Symfony code
  • Extension mechanisms built on Symfony tools like actions, components, templates and partials
  • Strong media repository
  • YouTube API integration
  • Active developer community
  • Per-page user permissions
  • In production use
  • Stable and mature

Cons

  • Current version is Symfony 1.4-based; will be rewritten for 2.0 as/when 2.0 stabilizes
  • Installion is complex
  • Interface needs work
  • Lack of LDAP/Active Directory/Open Directory Integration

Slate

Pros

  • In-context inline editing
  • Intuitive interface
  • Multiple site management/support
  • Easily extendable via Plugin/Components
  • Content can be updated via IDE/Text Editor as well as web interface
  • Versioning

Cons

  • Lack of LDAP/Active Directory/Open Directory Integration

Shopify

Pros

  • Intuitive interface
  • In-context inline editing
  • Built in shopping cart
  • Easy extendable API
  • Easy to theme

Cons

  • Commercial
  • Hosted

Magento

Pros

  • Zend Framework
  • Built in shopping cart and Content Management
  • Very flexible extendable API
  • Opensource with optional commercial support

Cons

  • Community edition lacks features found in commercial offerring
  • Interface can be overwhelming

ExpressionEngine

Pros

  • Easily extendable via Plugin/Components
  • Great documentation and books are available

Cons

  • Interface was better in v1.6
  • Lack of built in LDAP/Active Directory/Open Directory
  • Lack of In-context/Inline Editing
  • Setting up multiple sites and managing them needs to be improved upon

Symphony

Pros

  • Clean looking interface
  • XML/XSLT Templates

Cons

  • Lack of built in LDAP/Active Directory/Open Directory
  • Lack of In-context/Inline Editing
  • Setting up multiple sites and managing needs to be improved upon

MailChimp

Pros

  • Email CMS/Manager
  • Easy system for creating email templates
  • Built in address book/contacts manager
  • Built in Web Analytics
  • Intuitive Interface

Cons

  • Lacks full CMS capabilities
  • Commercial
  • Hosted

Wordpress

  • One thing that’s handy with Wordpress is that templates are not tied to specific datatypes. This is really handy as you don’t need to extend or re-implement a datatype just so that you can have a different template.

Silverstripe

  • Clients always love Silverstripe’s administration section. It’s desktop-app-esque and that’s familiar to users. We (Pixel Fusion ) have created a similar interface for our internal Symfony CMF utilising Sencha’s
    ExtJS

PimCore

Pros

  • In-context/Inline Editing
  • Drag & Drop Media

Cons

  • Lack of built in LDAP/Active Directory/Open Directory
  • Interface needs work

eZ Publish

Pros

  • Open Source
  • MVC
  • Extensible
  • Content meta model with possibility to define different pages types
  • Worklfow and Trigger
  • OpenOffice import/export
  • Webdav support to upload documents and images
  • Community
  • Frontend editing
  • Clustering support
  • Advanced policies system
  • Advanced caching system

Cons

  • Interface needs overhaul
  • Lack of built in LDAP/Active Directory/Open Directory

Drupal

Pros

  • Massive use base
  • Massive archive of modules to extend the core
  • You can almost build a complete, complex, website not even touching the code
  • OpenSource
  • “Everything is a node” makes it easy to understand the concept for an user
  • Easy to start, no “programming” skills needed

Cons

  • Not MVC
  • Not (yet) fully ready for PHP 5.3.x
  • Modules aren’t moderated very well
  • “Everything is a node” makes it hard to do special enhancements
  • “Everything is a node” together with lack of decent architecture makes database model nasty
  • “Everything is a node” makes it hard to tweak db performance