Other open source content management systems
Below is a table of open source content management systems I evaluated but which I decided not to recommend. For each, I give the main reasons why I decided not to recommend them. This is not to say that they would be appropriate for some organisations; rather, they didn't meet the criteria I specified.
Note: This review was written in May 2005, so the statements below reflect the state of these systems at that time.
| System | Homepage | Reason for not recommending |
|---|---|---|
| AngelineCMS | http://www.angelinecms.org/ | Unstable; default templates not very polished |
| CPG-Nuke | http://www.cpgnuke.com/ | Templates complex to edit |
| CPS | http://www.nuxeo.org/ | Similar to Silva, but not as full-featured |
| Daisy | http://new.cocoondev.org/daisy/ | More of a framework than a complete CMS; difficult to host and configure |
| e107 | http://www.e107.org/ | Still in early stages of development |
| eNvolution | http://www.envolution.com/ | Inflexible; default install is broken |
| eZpublish | http://www.ez.no/ | No free WYSIWYG editor; licensing is complicated; incompatible with Apache 2 |
| Exoops | http://www.exoops.info/ | Poor documentation; lacking features |
| eZContents | http://www.ezcontents.org/ | Poor documentation; default templates use frames |
| Geeklog | http://www.geeklog.net/ | Difficult to write own themes; few features |
| Jetstream | http://streamedge.com/ | Confusing interface |
| LDU | http://www.neocrome.net/ | Poor documentation; confusing interface |
| Magnolia | http://www.magnolia.info/ | Requires J2EE server; difficult to install and configure; more of a framework than CMS |
| MD-Pro | http://www.maxdev.com/ | Complicated interface |
| Midgard | http://www.midgard-project.org/ | Installation requirements extensive (e.g. requires installation of PHP module) |
| myPHPNuke | http://www.myphpnuke.com/ | Default install doesn't work |
| Nukes | http://jboss.com/products/nukesjboss | Templates restrictive; code highly "designed", but consequently difficult to follow! |
| OpenCMS | http://www.opencms.org/ | Java-based, so harder to host; huge code base (difficult to modify); complex; default install would require a lot of "cleansing" before you got a usable site |
| Ovidentia | http://www.ovidentia.org/ | Default templates not cross-browser compatible; documentation in French |
| phpwcms | http://www.phpwcms.de/ | Documentation sparse; some features still under development; fiddly interface |
| phpWebsite | http://phpwebsite.appstate.edu/ | Primitive access control; hard to organise content |
| PHPX | http://www.phpx.org/ | Default templates don't display correctly |
| PostNuke | http://phpnuke.org/ | Menus very difficult to follow |
| Props | http://props.sourceforge.net/ | Very focused on newsletter publication but few other features |
| Renegade | http://www.renegade-cms.com/ | Still under heavy development |
| RunCMS | http://www.runcms.org/ | Requires lots of manual configuration; sloppy default templates |
| TikiWiki | http://www.tikiwiki.org/ | Poor SQL; very intensive on the database back-end; clogged interface |
| TribalCMS | http://tribalcms.com/ | Although it looks promising (nice simple interface and easy to install), it is very buggy on my setup |
| Typo3 | http://typo3.com/ | Complex to modify; doesn't work well with non-IE browsers |
| WebGUI | http://www.plainblack.com/webgui/ | CGI based (less secure); exotic Perl requirements; requires tuning to perform well |
| Xoops | http://www.xoops.org/ | Similar to Xaraya; difficult to work out how to add simple HTML pages; cluttered default layout; difficult to extend, as the API is limited |
Search
Created with the Plone Content Management System.
Unless otherwise stated, content on this site is licensed under the Creative Commons
Attribution-NonCommercial-ShareAlike License