Skip to main content

The Evolution of Content Management

Edit: Seems Writely doesn't publish images onto here. Argh.

It is challenging to make a clear distinction that separates WCM systems from similar information systems. To explore this one must understand the possible ways to do web content management. Various architectures of implementation exist. One possible categorization is presented here.

These four levels are a way to divide the physical management of content. In general one can say that the higher use of web content in a company, the higher level its WCMS implementation should be. The separation is historical and drawn from my personal experience with web development through the last decade, therefore the evolutionary approach.

Static files on a web-server

The most basic strategy is to compose static HTML files and transfer these to a web server capable of serving such files to clients connecting to the web-site. It is possible to apply styles to the pages, for example with the help of cascading style-sheets (CSS).

Content wrapped in templates

The next level of content management is attained when the editor wishes to re-use the design of the web-site by dynamically including content into a frame of finished design, or a template. The content is typically contained in a text file the dynamic page engine

can read. Examples of technology capable of this are Server-Side Includes (SSI), Simple Common Gateway Interfaces (CGI) [Dudek, 2003] and XML-documents using XLST transformations [Weitzman, 2002]. The HTML standard also has a command called frames to include nested web-pages, although professional web designers and developers frown upon the use of this deprecated function [Nielsen, 1996].

Dynamically generated content

More complexity arrives as the re-use of templates is pushed further, having a template dynamically selecting content source based on a dynamic parameter. This is not possible with SSI as you have to provide each separate content page with its own physical HTML file. This means two files for any page on the web-site, one with content, another with design. Many find this to be too cumbersome and end up putting both files inside one, thereby mixing content and design. If a dynamic parameter is possible, as is the case with scripting languages such as PHP (a recursive acronym), Active Server Pages (ASP) or JavaServer Pages (JSP), one can have the template select and read the content file conditionally, thereby removing the need for its own HTML file [Challenger, 2005].

Content stored in a repository

The next step is to remove the content files to replace them with something more scalable. Native files have many disadvantages: they are not versionable, backup-routines require mirrored copies, search is not easy, binary files like picture and video can not be wrapped with meta data, there is no fitting access control and the possibilities for collaboration is limited. Instead the content is put inside some kind of repository, most likely a database, illustrated in Figure 5. Management of the content is subsequently handled by middle-ware that replace the programming interface of the file system.

A system developer will recognize this three-level architecture of the Model-View-Control (MVC) pattern [Reenskaug, 1978]. The model consists of the content in the database, the view-layer is provided by templates, and control is implemented in the middle-ware. The MVC is a pattern that offers a separation of concerns in the WCMS.

The next level

It is possible to invent further levels of content management, but any present form of WCMS will most likely apply some variation of the last level. Future levels might include technologies focusing on content integration and service orientation with the use of web services and mash-up principles [First Author, 2006]. Another direction in improving performance is distributed CMS networks [Voras, 2005], [Canfora, 2002].

Canfora, G., Manzo, S., Rollo, V. F., Villani, M. L. 2002, "ContentP2P: a peer-to-peer content management system", conference proceedings from COMPSAC'02, IEEE

Challenger, J., Dantzig, P., Iyengar, A. 2005, "A Fragment-Based Approach for Efficiently Creating Dynamic Web Content", 2, p. 359-389

Dudek, D. T., Wieczorek, H. A. 2003, "A Simple Web Content Management Tool as the Solution to a Web Site Redesign", conference proceedings from SIGUCCS'03, ACM

First Author 2006, "The Monster Mash-Up" [http://www.firstauthor.org/research_tools.html#Mashups] Retrieved 22. April, 2006

Nielsen, J. 1996, "Why Frames Suck (Most of the Time)" [http://www.useit.com/alertbox/9612.html] Retrieved 22. April, 2006

Reenskaug, T. M. H. 2006, "MVC XEROX PARC 1978-79" [http://heim.ifi.uio.no/~trygver/themes/mvc/mvc-index.html] Retrieved March 26, 2006

Weitzmann, L., Dean, S. E., Meliksetian, D., Gupta, K., Nianjun, Z., Wu, J. 2002, "Transforming the Content Management Process at ibm.com", Experience Design Case Study Archive

Voras, I., Zimmer, K., Zagar, M. 2005, "Distributing Web-based Content Management System - "FERweb"", conference proceedings from ITI 2005,

Labels:

Comments

Post a Comment

Popular posts from this blog

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --...
12 comments
Read more

Git-SVN Mirror without the annoying update-ref

This post is part of  a series on Git and Subversion . To see all the related posts, screencasts and other resources, please  click here .  So no sooner than I had done my git-svn presentation at JavaZone , I got word of a slightly different Git-SVN mirror setup that makes it a bit easier to work with: In short, my old recipe includes an annoying git update-ref step to keep the git-svn remote reference up to date with the central bare git repo. This new recipe avoids this, so we can simply use git svn dcommit   directly. So, longer version, with the details. My original recipe is laid out in five steps: Clone a fresh Git repo from Subversion. This will be our  fetching repo. Set up a  bare repo. Configure pushing from the fetching repo to bare repo In the shoes of a developer, clone the repo Set up an SVN remote in the developer's repo In the new approach, we redefine those last two steps: (See the original post for how to do the fir...
17 comments
Read more

Syncing your Git repo with the Subversion repo

This post is part of  a series on Git and Subversion . To see all the related posts, screencasts and other resources, please  click here .  This is a follow-up to the previous post on how to live with Git and Suversion in parallel . It's really trivial stuff for any experienced user, but was worth noting down somewhere for my own sake. I've cloned a project called "fudge" from Subversion: >git svn clone https://scm.mycompany.com/svn/fudge So my local repo has the correct svn-remote configuration and all that to go with it inside fudge/.git/svn . This is done automatically when you svn-clone. The bad thing is that all my Git-mates at work have to wait for me doing svn-rebase before they can pull the latest code from Subversion from my repo into theirs. I want to get rid of this responsibility. I'll put something similar to my svn-rebasing repository on a server, have it run svn-rebase regularly, and push the changes to a centralized git repository, ...
6 comments
Read more

Git-SVN Mirror for multiple branches

This post is part of  a series on Git and Subversion . To see all the related posts, screencasts and other resources, please  click here .  This extends the posts where I explained how to set up a git-svn mirror for a single directory. NOTE: If you just want to use Git against a SVN repo on your own, stop reading ,now, and stick to the git-svn basics. However, if you want a setup where you can share a Git repository with colleagues and friends while still interfacing with Subversion, keep reading. I'll show how to set up a git-svn mirror for a standard Subversion project with trunk , branches and tags . It's a bit like the single directory mirror, but in order to keep all branches in sync, it's a bit more fiddling. The good part is that this setup enables us to cherry-pick commits from one branch to the other. This is slightly smoother than using svn merge . First of all, let's repeat how our Subversion and Git-repositories look physically (roughly the sa...
13 comments
Read more

Git+SVN #5: Centralized Git-SVN Mirror

This post is part of  a series on Git and Subversion . To see all the related posts, screencasts and other resources, please  click here .  Another episode on how to live with Git and Subversion in parallel: Only a few days left till GearConf, where I will be repeating the exercise, adding all sorts of useful hints and tips on the way. NOTE : At the end of the cast, I presented this little shell-script that I normally use for committing: #! git update-ref refs/remotes/git-svn refs/remotes/origin/master git svn dcommit Some more background: git svn dcommit actually updates the refs/remotes/git-svn However, in the case that I first do a git pull from the bare repo, getting the new commits via the "pure" git command, no svn refs are updated! Example: Let's say bob commits a change. John then updates his repo: tfnico@flint:~/john/website/> git pull --rebase remote: Counting objects: 8, done. remote: Compressing objects: 100% (4/4), done. remote: ...
12 comments
Read more