How To Choose An Open Source CMS 191
An anonymous reader writes "Content management specialist Seth Gottlieb has written an easy to understand how-to on selecting an open source CMS. Gottlieb is also responsible for the whitepaper 'Content Management Problems and Open Source Solutions' which summarizes 15 open source projects and distinguishes between open source CMS and proprietary software selection."
Etomite (Score:2, Interesting)
Good points so far:
- Simple to setup
- Easy to develop templates for, our template (http://www.intellipool.se/ [intellipool.se] took a work day to put together.
- The back end is easy to use and provides nice editing features directly in the browser.
Drawback:
- If you are looking for something that can do "everything" and be extended left and right, Etomite is not for you.
www.etomite.org
Structure (Score:5, Interesting)
There are other choices that can quickly filter CMS's, but many of the choices have alternatives or can be hacked around. Only rarely will you find a CMS that can handle both navigation structures.
Too Many (Score:4, Interesting)
Drupal gets my vote (Score:2, Interesting)
Re:CMSes are going the way of the dodo.. (Score:3, Interesting)
Re:Hm, an OpenSource CMS? (Score:1, Interesting)
CMS Made Simple (Score:2, Interesting)
PHPwcms is excellent (Score:2, Interesting)
That said what CMS you choose - open source or otherwise - is entirely predicated on the project. Got a community site? Take a look at Drupal or Mambo, maybe something smaller if it works. Need a small content site? Check out PHPwcms, CMS Made Simple, or LucidCMS. Someone else mentioned Etomite, but Etomite is quirky, visually unsophisticated (the admin tool looks a little garbagy), and lacks some of the flexibility provided by other tools.
PHPwcms' management of content as small objects that can be easily called or reused in secondary locations (allowing you to have a repository of "global" content was a huge argument in favor of it for my project. Its only major weakness is the lack of robust entitlement capabilities... its been on the books for a year, but no one has developed it further... you can only set-up an all Admins or vry weak content administrators (who can't edit content).
-rt
Re:Non open-source CMS no good ? (Score:1, Interesting)
It is slow and you can't have 10 editors working at the same time without melting the server...
Also the JSP is put inside the templates... Your templates can kill the server, wow!
Next product please !
Re:Best CMS (Score:3, Interesting)
Re:Good multilingual support? (Score:3, Interesting)
Not only does it have multilingual support, the workplace is pretty well localized (english, german, japanese, etc)
It is a java application, so if you want all this in php, you'll need to look elsewhere.
Re:Hm, an OpenSource CMS? (Score:2, Interesting)
Re:Go Native among the Users (Score:3, Interesting)
The most critical feature for our choice of a CMS was the interface for the content editors. My customer is a small company. The content editor was basically a secretary with few technical skills. I could program anything, but the editing interface had to be simple to use. (The second critical feature was the price. Part of the reason we won the contract was the budget did not include any commercial software.)
We chose Apache Lenya. It comes with two editors: Kupu and BitFlux, and there are several others that integrate easily. We chose to standardize on Kupu because the interface looks like MSWord. (It also has a "View Source" button so I can fix whatever the editor breaks.) There were a few support calls in the first month, but a one page cheat sheet solved that. A new editor took over, and the only support call was for a copy of the cheat sheet.