Ultimately, the purpose of a Content Management Software package is to create and environement where an entity can focus on the content of said site rather than the coding. Ideally, a CMS would be put in place to ease workload on all parties – the developer(s) spend less time updating content that they may not have any attatchment to or understanding of, and content providers don’t have to worry with the technology – just the quality of the content.
I am currently in the process of testing as many pre-packaged CMS’s as I can. Right now, I have Subdreamer and Joomla running while testing MANY add-on modules, and I am obtaining several more from sourceforge. I plan on sharing my findings with each, but ultimately it comes down to the discussion proposed by this topic: which is better? The custom job specific to your needs, or a pre-packaged solution.
First, let’s start with a Custom CMS:
Pros:
Cons:
Pre-Packaged Solutions
PROS:
CONS:
I don’t know if this helps or not, but it does at least give some frame of reference for choosing a solution. Like I said, there will be more on the specific CMS’s that I test, specifically feedback on administration and overall presentation, but this is a starting point.
One Response
bofe
February 12th, 2007 at 1:33 pm
1One thing you’re neglecting is that some prepackaged CMSes cost money. Not all of them are free/open source.
I’ve been down this road thousands of times, so I’ll add some of my war-torn input:
- Only dealing with one organization/site? Go with a prepackaged.
- Dealing with a ton of sites with similar, specific needs? Go custom.
It really depends on your org needs and cost/benefit. Why does your org. need a CMS? What benefit is having “current” easy to update content going to have on your business’ bottom line?
Anyway… Take care.
RSS feed for comments on this post · TrackBack URI
Leave a reply