Skip to main content

Digging deeper into CMS requirements (#3: End-user Requirements)

This is the third post about digging deeper into content management requirements. See also
Today I'm gonna run through two categories of requirements. They both have to do with how the CMS is portrayed towards the end-user, through translation and delivery.

Globalization

International companies need multilingual web-sites [Huang, 2001] with internationalization and localization features.

Internationalization

This is the concept of having country and language-specific content, essentially having the main content of the web-site translated to one or more languages [Iverson, 2002].

Translation of a WCMS can be divided into two parts. The most important one is how the content itself can be translated by the content managers. The other aspect is the language of the WCMS itself regarding internal interfaces for administration and management.

Localization

This refers to visual effects based on the visitor's locale, like country specific temperature, time, date and currency formats, one example being how certain countries use the 12-hour AM/PM style to define time, while others use 24-hour notation.


I would like to add the following:

Do not internationalize your site if you don't really really need to. If you can get away with it, stick to one language, either English or the local language. Doing i18n and l12n is easy to describe in principle, but oh-so-heavy and difficult to implement and maintain, both technically and content-wise.


Content Delivery

Syndication

To increase the availability of content, larger web-sites feature syndication, or off-site publishing. This can be approached by subscribing to receive new pages through e-mail (newsletters), or as the increasingly popular news-feed (RSS).

As an example, many news-sites have offered the option of subscribing via RSS-feeds. By subscribing to these feeds in RSS-readers or news-aggregators, the process of collecting news from these sites is turned from a pull-protocol, actively browsing for content, into a push-protocol where content is pushed to the reader.

This is related to the idea of the Semantic Web [Berners-Lee, 2001], a set of W3C standards created for enabling data sharing across the Web. One version of the RSS format (1.0) is actually a name-space within the Semantic Web's RDF specification.

Accessibility

Many developers associate accessibility with the extent on which disabled people can use computers. This could be because they lack motoric skills, or because their hearing or eyesight is impaired. For example, certain keyboard shortcuts would not be accessible for a one-handed person, and color-codes can be hard to read for the weak-sighted.

A more generic understanding of accessibility is the limitations readers have accessing content. These limitations can be lack of mouse or keyboard, small sized screen or lack of colors. Limited devices like mobile phones, PDAs and older computers lack the luxury of heavy graphical user interfaces.

Search

The importance of the this requirement is proportional with the size and maneuverability of the web-site. Although a very basic search-engine is sufficient for most sites, it is also possible to implement smarter searches that accord for miss-spelling, try different word ending(s), and use context specific dictionaries. A good search-engine also indexes your online binary files (PDF and Microsoft Office documents for instance).

The intelligence of a search engine increases by the work which is put into configuring it because there are a lot of context related parameters which must be sorted out. The engine must accord with language(s), location of where the searchable information is stored, possibilities for tracking content by URLs with spidering techniques and security. There are many issues which much be situationally decided, like whether hidden files should be search-accessible. Upon installation of the search engine, it will require hours of manual configuration to fit the context. It should be able to monitor the search patterns of the visitor to better tune the searches to yield usable results.

Communication

A powerful mean to further enable existing content is to give the consumer the opportunity to provide feedback to the web-site. This functionality can come in several shapes, including the ability to add comments to web-pages, participate in online surveys and discuss content in forums or chatting consoles.

If the goal is to make it easier for potential customers to contact the business, one could measure the number of visitors compared to the number of visitors who actually fill in some online contact form.

A way to generate income directly this way is to provide the visitor with the option to buy services through a web-shop. Having this channel makes it quite easy to measure how many sales are generated from the business' web front-end.

Feedback from visitors can collected to help improve the web-site, but some sort of incentive is normally required to tempt any visitors into actually completing such a form. If the web-site is of low value to the visitor, chances are slim that the visitor will aid improving the web-site.


References:

Berners-Lee, T., Hendler, J., Lassila, O. 2001, "The Semantic Web" Retrieved 29. April, 2006

Huang, S., Tilley, S. 2001, "Issues of Content and Structure for a Multilingual Web Site", conference proceedings from SIGDOC'01, ACM

Iverson, S. P. 2002, "Content Management Beyond English", conference proceedings from IPCC 2002, IEEE International

Comments

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities . It "was decided" that we'd be doing AES with a key-length of 256 , and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet! The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE  in order to do 256 bits. It's a fascinating story , the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them. Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password

The Git Users Mailing List

A year ago or so, I came across the Git-user mailing list (aka. "Git for human beings"). Over the year, I grew a little addicted to helping people out with their Git problems. When the new git-scm.com webpage launched , and the link to the mailing list had disappeared, I was quick to ask them to add it again . I think this mailing list fills an important hole in the Git community between: The Git developer mailing list git@vger.kernel.org  - which I find to be a bit too hard-core and scary for Git newbies. Besides, the Majordomo mailing list system is pretty archaic, and I personally can't stand browsing or searching in the Gmane archives. The IRC channel #git on Freenode, which is a bit out-of-reach for people who never experienced the glory days of IRC. Furthermore, when the channel is busy, it's a big pain to follow any discussion. StackOverflow questions tagged git , these come pretty close, but it's a bit hard to keep an overview of what questio

Git tools for keeping patches on top of moving upstreams

At work, we maintain patches for some pretty large open source repositories that regularly release new versions, forcing us to update our patches to match. So far, we've been using basic Git operations to transplant our modifications from one major version of the upstream to the next. Every time we make such a transplant, we simply squash together the modifications we made in the previous version, and land it as one big commit into the next version. Those who are used to very stringent keeping of Git history may wrinkle their nose at this, but it is a pragmatic choice. Maintaining modifications on top of the rapidly changing upstream is a lot of work, and so far we haven't had the opportunity to figure out a more clever way to do it. Nor have we really suffered any consequences of not having an easy to read history of our modifications - it's a relatively small amount of patches, after all. With a recent boost in team size, we may have that opportunity. Also the need for be

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone https://github.com/tfnico/config-mr.git mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git     -> ~/.atom/* config-mr.git     -> ~/.mrconfig     -> ~/.config/mr/* config-tmuxinator.git       -> ~/.tmuxinator/* config-vim.git     -> ~/.vimrc     -> ~/.vim/* config-bin.git        -> ~/bin/* config-git.git               -> ~/.gitconfig config-tmux.git       -> ~/.tmux.conf     config-zsh.git     -> ~/.zshrc How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for o