Why one project chose Drupal over Plone

Alexandra Samuel recently evaluated Plone, Drupal and a bunch of other CMS platforms for a project involving the creation of a network of websites that want to exchange a great deal of information via RSS.

In the end, she chose Drupal, mainly because it had built-in RSS aggregation features.

It was interesting to note [what she said about Plone](http://www.alexandrasamuel.com/telecentre-platform) in her writeup:

>As a CMS based on the Zope platform, Plone offers much greater programming extensibility than other CMS options we considered. The flip side of this virtue is that Plone’s relative advantages are much less compelling for a project that (like telecentre.org) specifically wants to limit its custom programming commitments.

>Ultimately our biggest concern was that Plone’s RSS aggregation capacity was not part of its standard install; while adding an aggregation module is a trivial technical challenge, the lack of native aggregation support spoke to the platform’s orientation towards single-site content management rather than distributed community.

One thought on “Why one project chose Drupal over Plone”

  1. Pingback: Blog

Comments are closed.