Jeffrey Veen is quite correct that Open source content management software sucks in a piece on his blog titled Making A Better Open Source CMS.
Open source content management software sucks. It sucks really badly. The only things worse is every commercial CMS I've used. But it really doesn't have to be that way.
Even closed source CMS's suck. You have people who have no User Interface experience coming along and telling you to change this do that and the user interface goes from bad to worse. Also the people who are designing the CMS aren't the people at the end of the day who have to use it.
Jeffrey says that various open source CMS have been written by geeks for geeks, which is true.
It was software written by geeks, for geeks. This whole category of software desperately needs to be redesigned with writers, editors, designers, and site owners in mind.
Here are my recommendations to the folks writing open source content management systems.
Make it easy to install. Your tool will see better adoption if you stop to consider the out-of-the-box experience before you ship it. I want to download, unpack, and run an installer in my browser. Ask me a few questions, and then you go set up the database tables and write the conf.php or whatever. Set constraints for yourself as you design this experience: 10 minutes from download to running, never send a user to the command line, never force open a text editor. It will be hard, but you're good at solving hard problems, and this is time very well spent.
I personally prefer an easy to edit config file for just the database details and maybe a couple of settings. Allowing users flexibility of what they can change is an art. Customisability without loosing functionality is key.
Make it easy to get started. Give first-time users a series of quick wins that become increasingly complex. When I first log in, I want to create a Web page. Next, I'd like to add some styles to it. Then, I'd like to make links to some other Web pages. I'll build a navigation system after that, and start to add other features eventually. But I want to feel successful with your system within a few minutes. I don't want to you to present the stunning power at my fingertips until I'm comfortable with my surroundings. Please save the content ranking, on-the-fly PDF creation, community forums, and user polls for later. I may eventually want that stuff, but not the first time I log in.
So do you give users the ability to go from a basic setup with help guidelines enabled to turning off the help/instructions at a later stage? Marketing people say things like our product is feature rich or carrier-grade without understanding the meaning of the words. I suppose that it is a selling point to use certain words in a way to market a product as being something it is not.
Continue reading "Jeffrey Veen hits the nail on it's head regarding CMS" »