smashingmagazine.com — Choosing a content management system can be tricky. Without a clearly de?ned set of requirements, you will be seduced by fancy functionality that you will never use. What then should you look for in a CMS?
Mar 5, 2009 View in Crawl 4
cloudberriesMar 6, 2009
I picked up Typo3 recently. It's a complete son-of-a-bitch to learn, but is quite the beast for flexibility.
silver26Mar 6, 2009
Silverstripe! <a class="user" href="http://www.silverstripe.org">http://www.silverstripe.org</a>
repmekevetsMar 6, 2009
<a class="user" href="http://dynamit.us">http://dynamit.us</a> for all your CMS needs.
dmurphyMar 6, 2009
This article is a just a list of features. It would be a lot more helpful if it actually compared the different CMSs.
alx359Mar 6, 2009
Design flexibilty etc are just parts of the initial phases of a web project. When a web project is done, what becomes central is further support and enhancements. Any custom-made CMS will quickly become legacy if there's no active development. Choosing the best long-term solution should be focused on developing and supporting in-house only the business differentiating features and their respective modules, where the core and all generic functionality should be supported by a (open source) community.
mtheoryxMar 7, 2009
I tried it, but I won't commit to using it until they get the CodeIgniter-based EE version 2.0 out (and who the hell knows when that'll finally happen after over a year of talking about it).