I then counted the CMS Matrix features that they lacked, as defined by a feature having a "No" or "Limited" or "Costs Extra" in a particular cell. One minus that value divided by the total number of features is given in the Pct Features column below. The "System Requirements" section was not tallied due to it's largely text content.
| CMS | Pct Features |
| TYPO3 4.5.2 | 97% |
| Plone 4.0 | 96% |
| WebGUI 7.9 | 89% |
| eZ Publish 4.2 | 83% |
| Joomla 1.6.0 | 82% |
| Drupal 6.10 | 77% |
| Xoops 2.0.18 | 71% |
| Mambo 4.6.1 | 71% |
| WordPress 3.0.4 | 63% |
| PHP Nuke 6 | 15% |
If you prefer the graphic, here's the same data set.
Perhaps tomorrow I'll dig out my copy of 'R' and see if these cluster in any meaningful way. I have the information summarized by each CMS Matrix category (Security, Support, Ease of Use, Performance, Management, Interoperability, Flexibility, Built-in Applications, and Commerce), so I'll be able to look at each section by itself in the days ahead. But one word of warning before you base a decision on these data, check the specific features you require against any candidate system. No need to throw out a possibility, if the reason is the lack of a feature you'll never use.
2 comments:
Just had a look at the feature comparisons between wordpress and plone. It doesn't look like either is very very accurate in the way those features lists are filled out. .e.g. no on multisite of WP?
So I think this particular statistic isn't worth much and may do Plone more harm than good.
I guess thats a cmsmatrix failing however.
It's true that since CMS Matrix info is supplied by volunteers almost certainly involved in a particular CMS, there can be biases and wildly uneven quality in the data. Not all terms and features are clearly defined.
That said, there must be some self-policing -- saying you have a feature that's not present could easily backfire in a viral way. Last I heard, Geir was taking care of Plone updates to CMS Matrix.
Post a Comment