CMSuck

Not too long ago, us folks at Southern Private University tech organization got a new CMS. Yesterday I got my first hand at what is now, officially, the CMSuck. I'm not a Web designer or any sort of expert, but my job is to take the mess of verbs, nouns, and punctuation marks that passes for writing in the tech world (sorry tech types, I call 'em how I see 'em) and make it more closely resemble written English and more usable to people who are not tech types. Thus, much of my time at work is spent repairing terrible writing and terrible design.

This year we're scrapping the terrible writig and terrible design and getting a new website, which I'm helping to populate using the CMSuck. And the CMSuck sucks hard. It might be fine in the technical functionality and all that, you know, stuff people who know more about software are concerned about. But frankly, that's not the most important thing about a CMS. People get CMS software so that the average user can change website content without mucking around in design or coding. And the problem with the CMSuck is that it's unintuitive and a pain in the ass for an average user like myself to use. It's more infuriating considering SPU tech organization spent literally two years before they picked out a damn CMS. It probably cost them a pretty penny, too, and I sit and ask myself, can we just get Drupal instead?