ceo at mbites media
25 February 2004 12:46pm
I'm currently working on a project to port a site to an open source content management system. There are various ones out there - many built in PHP for instance.
Perhaps people would like to register their vote for their favourite open source CMS?
Drupal? Zope/Plone? Etc? What do you think?
For my money, the Zope/Plone combination looks interesting...
Director at Solid State Group
25 February 2004 18:18pm
the old "whats the best open source CMS" thread.
I recently did a comparion of some of the top open source CMS' and I would be happy to forward that document to anyone who is interested in it. The results were skewed by the client who put far to much weight on the activity of the surrounding community.
Initially we were going to recommend InfoGlue, because it seemed like a sound product, and we wanted to work with something Java based, but in the end we went with OpenCMS, because of it's active developer community.
In hindsight, this was a mistake. OpenCMS doesn't split up the content from the presentation layer nearly enough. I find that to make a nice looking site in OpenCMS, I am having to put tables and formatting into the content area. Not good.
If I had the choice of all the free CMS's I think the 2 most interesting ones would be brickolage and the one from Squiz.net.
Bear in mind the cost of development for an open source CMS can sometimes be more than buying one.
26 February 2004 15:30pm
Many thanks, that's very useful!
The big issue for me is that many CMS are designed as community CMSs not full-blown publishing ones.
26 February 2004 16:17pm
My gripe with Open Source CMS solutions, (and I'm coding up a site in OpenCMS in my other browsr right now), is that as soon as they are released as open source, the momentum of development seems to just stop.
The classic path to open source is for a company to write a bespoe system for the client, then realise the code is reusable, so either take on the CMS as a new product and start selling it, or release it as open source and make cash for consultancy.
If it becomes a new product, it shoots up in price but tends to have major releases every 6 months to fix bugs and add nice features.
If it becomes open source, it's free (whahey!) but it hardly ever gets updated, and you will find yourself spendng a LOT of time wrestling with bugs that never get fixed, and delving through community email archives trying to find out how to use functionality that should be in basic documentation, and would be if someone were payed to write it.
So thats the choice, expensive, but quicker with good docs and support, or cheap but frustrating and long winded.
Thats my experience so far anyway... i hear that squiz.net CMS isn't like that, but then that might be marketing.
On 15:30:04 26 February 2004 mikegb wrote:
>Many thanks, that's very useful!
>The big issue for me is that many CMS are designed as
>community CMSs not full-blown publishing ones.
Technical Director at Box UK
02 March 2004 17:24pm
Just a quick additional note: for those that enjoy the challenge (and have the resources), an extensible solution could be to develop a CMS based on one of the proven 'frameworks' that have been developed, e.g. Zope (http://www.zope.org/) or Cocoon (http://cocoon.apache.org/).
These automatically handle some of the large-architectural aspects of CMS's (modularisaion, presentation layer, storage, etc.), but allow you the flexibility to develop an interface and publishing system on top.
Probably more costly than buying a mid-range CMS, but it's another option...
Free market research on digital marketing
Daily Pulse: award winning newsletter
It takes 30 seconds to register