Hands off the content management system

Is a content management system (CMS) a tool to democratise content creation or should it only be used by web professionals?

Play

I remember vividly the pre-CMS era. Over worked web designers whose job was reduced to fixing typos and marketing people frustrated by the bottleneck that was the web team.

The democratisation of content creation

The arrival of content management systems felt like heaven descending from on high. Finally the web designers could go back to their job of designing and building sites, while the marketers and other content creators could manage their own content without having to wait.

Of course nothing is ever that straightforward. Content management systems were not the best designed things in those early days and the learning curve was steep. However, things did improve over time and training got better.

Now anybody with basic computer skills is more than capable of putting content online. The web was no longer the domain of those who understood acronyms like HTML and FTP. Content creation had been democratised and everybody was invited.

This all sounds great in principle, but some argue it has created problems.

The problem with open access

Unfortunately providing open access to edit a website is not without its risks, especially within an institution that has certain standards it wants to maintain. It also has an impact on the usability and accessibility of a site.

Using a CMS to design

For a start many content creators are using the WYSIWYG editors built into most content management systems as a way to alter the design of a site. They are setting typography, imagery and colours that no professional designer would ever sanction. Some argue this undermines the brand of organisations, damages the user experience and undermines accessibility.

Example WYSIWYG editor in a CMS
Content providers are using content managements systems to make design changes, rather than simply editing content.

Poor writing skills

There is also a feeling in certain quarters that many content creators are not equipped to write quality content for the web. People read in a particular way online and there are considerations to take into account. Many are not experienced in writing this way, even if they are good offline writers.

A lack of consistency

Finally there is an issue of consistency. With multiple content creators across the organisation all updating the site, the chances of inconsistency in style and information is high. A website quickly ends up with a fragmented voice that further undermines brand and usability.

Stricter control? More training?

There is normally one of two responses to these challenges. Either an organisation invests more in training (in the hopes of teaching people best practice) or they implement ever stricter policies. It is rare for either approach to succeed.

Training can work when people are using a content management system on a near daily basis, but most content providers are not. By the time they come to next edit the site they have forgotten most of what they have been taught.

Stricter control suffers from a similar problem. Organisations lay down guidelines that people forget about or fail to follow.

Some success has been seen by removing WYSIWYG editors or adding workflows and permissions. However, it could be argued that these are merely papering over an underlying problem.

Perhaps there is a better way.

Manage content centrally

Some are suggesting that the role of a content management system is not to democratise content production, but rather to speed the creation and editorial process.

They go on to suggest that on that basis content management systems should only be used by dedicated web professionals. This does indeed address many of the problems.

These people would be working under central editorial control and so their output can be monitored for consistency. Also because they are working on the website daily, they become experienced with writing in the appropriate tone of voice and within the organisation’s brand.

Of course you could argue that this just creates a bottleneck, like in the pre-CMS days. However, that may not actually be the case because a CMS is much faster than coding stuff by hand.

In addition dedicated staff who are veteran CMS users, experienced in writing for the web, are likely to be considerably faster than somebody who updates a page once every few months.

Up for debate

Not that everybody agrees this is the route content management should take. Some like the idea of anybody being able to update content and others claim that having a professional team is impractical. With that in mind, I would like to discuss this on the podcast. Our debate topic is therefore:

This house proposes that content management systems should only be used by web professionals.

Do you agree? Is the proposal even practical? How would you define a web professional? Let me know in the comments.

  • richarddale

    I definitely think mobile sites have their place. Many of the sites I built prior to RWD, static sites that view great on desktop and tablet. Its only when you get down to smart phone size that things start to break down. For many of these sites a mobile specific site would probably work better than a RWD site where I could be more focused and target the medium specifically.

    I did a RWD e-commerce website recently and although the end results were good, trying to get the shopping basket working and looking correct whilst being responsive was a nightmare and I couldn’t help but think that a mobile specific site would have been a better solution. When I browse the web using my iPad Air I never visit a fix width website and think this is a poor user experience why don’t they have a RWD site. I ony ever think this when on my iPhone.

  • sanedevil

    I am not a web designer, but have a team that is building one for me. So in trad way, I have to have a “web designer” design the site in Photoshop which is then handed to “web developer” to generate code.

    You can imagine there are several problems w this – time, costs, rework, code doesn’t do what the design shows etc.

    I hit upon your blog while thinking if there are tools that would eliminate the design-to-code step

    I very much agree w the house and would love to know the process and tools to help achieve this.

Headscape

Boagworld