Hacker News new | past | comments | ask | show | jobs | submit login

The problem with CMSes that have "all the features you want" is that they have so many features that the average user who just needs to plonk some content down on a page and periodically edit it can't wade through all the features to figure out how to do that.

(I don't say this to pick on Plone -- I'm a big fan of the TYPO3[1] CMS, for instance, which does lots of the things that he mentions very well, but the downside to that power is that it's insanely hard for normal people to pick up and use.)

[1] http://typo3.org

A few years ago i recommended website baker as a nice simple CMS, which is also hackable if necessary. That was three years ago. Maybe the situation has changed, but i would never recommend a complexity-monster like Typo3. Typo3 is "enterprisy" in the negative sense.


Don't be too hard on TYPO3, it has its virtues. For instance, it has the most elegant handling of multilingual content I've ever found in fifteen years of working with CMSes. But for a small single-language site (i.e. 99% of the sites people develop) it's definitely overkill.

For as complex as it is, TYPO3 is pretty usable. I built a site on TYPO3 before I ever messed with WordPress some 6 years ago. Now that I think of it, I'd probably opt for TYPO3 before Drupal.

CMS is a grown-up software.

Selecting and using a CMS requires time, preparation and mostly importantly a budget. If you haven't considered the any of these, then you can't really afford a CMS.

This is an awesome way to rationalize writing software that nobody uses.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact