Introduction to Content Management Systems

Spend your time managing information, not technology

Download the whole article as PDF

Short URL: http://fsmsh.com/1262

Write a full post in response to this!


In the beginning, the web was simple. You used Mosaic to browse it. You used a text editor to construct pages on it in a language called HTML. If you weren’t a techie, you probably didn’t even know it existed. Then people realised that even non-techies had useful information (“content”) to share. So the Content Management System (CMS) was born.

What is a CMS?

At its heart, the web is a tool for sharing information. To make it possible to display that information (or “content”) on a variety of different machines, people devised a language (HTML) that told the machines how to display it. From the machine’s perspective, this was great: it helped separate information from mere formatting. From the perspective of someone who wanted to share information, it wasn’t so great: they now needed to learn HTML in order to publish their content.

CMSs were developed to resolve this dilemma. A CMS helps you create and store content in a shared repository. It then manages the relationships between content items for you (e.g. keeping track of where they fit into the site hierarchy). Finally, it ensures that each content item is connected to the right style sheet when it comes to be published. Some CMSs also provide facilities to track the status of content items through editorial processes and workflows.

By using a CMS, content editors and the organisations they work for get a number of benefits. For example, they can:

  • Create and publish content in a standard format without needing to know HTML or other languages;
  • Co-ordinate the work of teams of authors and editors (e.g. by ensuring that only one person is editing any individual content item at any one time);
  • Control the branding and quality of content (e.g. by ensuring that the correct style sheets are applied, and that changes to the content are approved before they are published);
  • Reuse the same content item in multiple different sites and formats.

A CMS can make it easier to create and publish content, to co-ordinate teams of authors and editors, to control branding, and to reuse content across multiple channels

Case Study—Oxfam

Oxfam is an international confederation of organisations that are working to find lasting solutions to poverty, suffering and injustice. Its websites, built on the Plone content management system, help build public understanding of poverty and its causes. By using Plone, people across Oxfam can collaborate and create engaging content without getting caught up in technical details.

Being free software, Plone was particularly relevant to Oxfam. Hugh Wallace, Oxfam’s Head of Interactive Media, notes:

“As Oxfam works in over 70 countries around the world, we were looking for a system that would enable us to share information across the organisation and beyond. Plone was the right choice and we’re very pleased to have the opportunity to work with the free software community. Investing in free software is win-win for Oxfam as we meet our needs but also know that the technology developed will be of benefit beyond Oxfam, particularly among other Non-Government Organisations.”

Public view. Oxfam is working to eliminate poverty, suffering and injustice. Its public website helps build understanding of poverty and its causes
Public view. Oxfam is working to eliminate poverty, suffering and injustice. Its public website helps build understanding of poverty and its causes
Behind the scenes. Using the Plone free software CMS, Oxfam’s authors and editors maintain the website without worrying about complex style sheets—Plone automatically generates a consistent look and feel for them
Behind the scenes. Using the Plone free software CMS, Oxfam’s authors and editors maintain the website without worrying about complex style sheets—Plone automatically generates a consistent look and feel for them

How have Content Management Systems evolved?

Until about 1996, most people managed websites by editing HTML files and uploading them to their web servers. As well as creating a barrier for non-technical users, this made it hard for organisations to build consistent messaging into their websites. As companies rushed to get onto the web, this was a problem—they wanted to get their content out quickly, but at the same time they were scared of losing control.

Early CMSs were developed to address this problem. A number of large, expensive systems were very successful because they allowed a small group of knowledgeable people to take control of an organisation’s content. CMS vendors thrived during 1996-1999 as the dotcom boom created large demand for their products, and they developed some highly sophisticated tools.

By 2000, the dotcom boom was cooling and the CMS scene cooled with it. During 2000-2003 the first wave of major vendors consolidated and the pace of development slowed. However, during this period a number of new vendors recognised that many organisations didn’t need a highly sophisticated tool—they needed a “good enough” tool at a lower price. A second wave of CMS vendors started to deliver these tools.

During this second wave, free software content management came into its own. The web thrives on openness and collaboration, and many very capable CMSs were developed to work within this spirit. There is now a thriving marketplace of free software CMSs. Some of these provide basic, easy to use functionality for individuals and small organisations. Some of them provide advanced functionality for more complex organisations.

Case Study—Lynne Azpeitia

For consultant and psychotherapist Lynne Azpeitia, working with talented and creative people means engaging with them at multiple levels. “It’s hard to get people’s attention these days. I need a way to connect to them and work with them so the message can get through. I’m constantly trying to create new ways of putting things together so that people can learn about themselves and develop themselves.” Audio, video, wikis, pictures, articles, teleclasses—they all need to be in the mix.

Lynne doesn’t pretend to be a technical guru. So she’s working with technology change artist Nynke Fokma to rebuild her site on the Joomla free software CMS. Once the site is ready, Lynne will be able to create, manage and update the multi-channel, multi-formatted content herself.

They’ve chosen Joomla for its ease of use. The visual administration interface works for Lynne, and means she’ll be able to manage the site without needing to know any coding. And for Nynke, the system is “freakishly flexible”—easy to make changes, easy to add functionality, easy to transfer content from the existing site. Just the thing for working on the edge of creative chaos.

Don't miss out on the other pages!
12next ›last »

Write a full post in response to this!

0

Do you like this post?
Vote for it!

Copyright information

This article is made available under the "Attribution" Creative Commons License 3.0 available from http://creativecommons.org/licenses/by/3.0/.

Biography

Graham Oakes: Dr Graham Oakes is the principal of Graham Oakes Ltd, a consultancy formed in 2003 to help organisations untangle the complexity within their systems, processes and governance. He helps define business and technology strategies that people will adopt, and then to assure implementation of those strategies. He can be contacted via his web site.

marienoelleb's picture

An interesting introduction, but important products were missing

Submitted by marienoelleb on Wed, 2006-08-02 09:31.

Vote!
0

Thank you for this interesting introduction to the WCMS. I was however surprized about the fact that some very important solutions were not mentionned.

The most important one is TYPO3, which has thousands of users, including large compagnies like Serge Dassault and political institutions like the European parliament and a very living community. The wealth of extensions developped for this WCMS is a striking proof of its wide audience.

Although OpenCMS is more a framework which is appropriate if someone wants to develop a WCMS closely adapted to its needs (and tightly integrated with J2EE applications), TYPO3 is an entreprise WCMS based on a core completed by the (existing) extensions needed in order to satisfy the need of a client.

I was also surprized to see that XOOPS was not even mentionned, while it is a very popular tool.

Another WCMS which would have been worth mentionning is the french SPIP. This editorial WCMS also has a very living community, thousands of users and it is, at least in french, very well documented. One of its interesting aspects is that it is used both by publishers (especially "Le Monde Diplomatique", a prestigious publication, the french government and countless non profit organizations and associations).

Best regards

Marie-Noëlle Baechler
Belmont-sur-lausanne / Suisse

Anonymous visitor's picture

Hello where is Drupal

Submitted by Anonymous visitor on Mon, 2006-08-28 09:36.

Vote!
0

Hi there,
I dont find Drupal on this list. This site seems to be running Drupal btw.
Hehe funny you left out the CMS you are running.

Dave Guard's picture

Actually...

Submitted by Dave Guard on Mon, 2006-08-28 13:10.

Vote!
0

Actually, we changed over to Drupal after this article was written.

There are so many CMSes to choose from; I imagine that the author covered the ones he is most familiar with.

Anonymous visitor's picture

Give the author a break

Submitted by Anonymous visitor on Wed, 2006-09-20 10:19.

Vote!
0

When the author says "Here’s my personal run down of some of the major free software CMSs. It certainly isn’t comprehensive, " seems to me there's no need to shoot the poor man!



Two fantastic free software companies that make Free Software Magazine possible:

Other sites

Odiogo