That's the opening line of this article over at Boxes and Arrows. They've posted some good tips, like "keep your team small" and "only build what you need." If you're evaluating a CMS, you should definitely check the article.
I think the problem with CMS is expectations. We've installed lots of content management systems for our clients. We've even built our own. Heck, we've fixed more CMS's than anything else! The only time we ever see a problem is when a client's expectations weren't set properly. Like when they expect to "not have to know HTML at all" but then also expect the system to be "totally self-sufficient." Meaning they never have to get any design or coding help---ever.
And it's not their fault. It's usually some slimy CMS salesperson that set those expectations.
They're kind of like cars, when you think about it. In the old days, you really did have to know how they worked to own one. You also had to wear goggles and a leather helmet, according to all those old-timey pictures on TV. Nowadays, you just buy-n-drive. But you still gotta take it in for maintenance, right? Oil changes here and there. A major tune-up every 30,000 miles or so.
When users (and CMS developers!) think that a CMS should be totally self-sufficient, expectations get out of hand, and things get into trouble. When CMS salesmen sell Ferraris to people who only need a Honda Civic, and then tell them it'll win races, fit all the kids in the back, hold your groceries, tow a boat, and never need maintenance, things go bad.
So here are some of our own tips for evaluating a CMS:
I think the problem with CMS is expectations. We've installed lots of content management systems for our clients. We've even built our own. Heck, we've fixed more CMS's than anything else! The only time we ever see a problem is when a client's expectations weren't set properly. Like when they expect to "not have to know HTML at all" but then also expect the system to be "totally self-sufficient." Meaning they never have to get any design or coding help---ever.
And it's not their fault. It's usually some slimy CMS salesperson that set those expectations.
They're kind of like cars, when you think about it. In the old days, you really did have to know how they worked to own one. You also had to wear goggles and a leather helmet, according to all those old-timey pictures on TV. Nowadays, you just buy-n-drive. But you still gotta take it in for maintenance, right? Oil changes here and there. A major tune-up every 30,000 miles or so.
When users (and CMS developers!) think that a CMS should be totally self-sufficient, expectations get out of hand, and things get into trouble. When CMS salesmen sell Ferraris to people who only need a Honda Civic, and then tell them it'll win races, fit all the kids in the back, hold your groceries, tow a boat, and never need maintenance, things go bad.
So here are some of our own tips for evaluating a CMS:
- Think of the CMS salesperson like a used car salesman (not that there's anything wrong with that).
- Write down a list of what you'll be using the
carCMS for. Editing the home page news? Maybe some press releases? - Understand that you'll need regular maintenance. How much can you afford? Can some of it be handled in-house?
- Know how long you'll need the
carCMS to last. How long did your previous website last, before you had to redesign it? 2 or 3 years is typical. When you get a new website, you'll probably want a new CMS, too. - Don't believe someone who tells you the
carCMS will last forever, thanks to some magical XML + CSS + RSS + content vs. structure doo-hicky. - Take them for a test-drive.
- Don't buy a Hummer when all you need is a Civic. And vice versa.
