So how about your Web CMS versus your KMS/CMS/Intranet?

Stand-Alone Web Content Management System

Many organizations have intranets on which they perform their content management duties. It is natural to propose that the WCMS integrates with the CMS. Parts of the content which should be exposed on the Web already exists somewhere in the CMS, perhaps on the intranet or on a central file server.

It is natural to believe that the best solution is to invest in a total solution where a CMS includes the WCMS by displaying the content with a Web interface. The case for choosing an isolated or singular standalone WCMS is explained below.

When selecting a system to control their web-site, decision makers are tempted to invest in enterprise solutions. These solutions promise to solve many of the corporate IT-problems with a single centralized silver bullet system. However, the projects where these solutions are selected, implemented and deployed often fail miserably, taking too long to complete. If they ever achieve nominal use, the requirements have changed and the system no longer satisfies the expectations of corporate presence on the World Wide Web [Robertson, 2006].

One way to avoid this pitfall is to build an internal lightweight WCMS, or to invest in an off-the-shelf product. There is still an understood need for such enterprise solutions in large corporations, but I am not sure any of the products in this category satisfies today.

For smaller organizations it is a viable option to leave web content management to a standalone system which is streamlined and specialized for the task.

The Differences between a CMS and a WCMS

A CMS and a WCMS have some traits in common. They contain some of the same content, like company and product information, and they might have similar content delivery methods. A CMS can be used to control the web-site. The company can make the knowledge base in the Intranet available online for allowing customers to troubleshoot problems themselves [Pelz-Sharp, 2006].

A WCMS can either be implemented as a front-end to the company's CMS, or as a stand-alone application. Since many companies have no suitable CMS in place, or their CMS lack a proper web front-end, the latter solution is likely the case.

If the web-site has a user name/password sign-on for employees, there is technically an “intranet” on the WCMS. This access control creates many possibilities for the system. As soon as the identity of an employee or member can be verified online, several normal content management processes can be performed inside the WCMS. The key advantage of doing content management online is portability. The users can access and modify content from anywhere in the world, as long as they have an Internet connection.

The next post will focus more on specific software alternatives (and links to where one can find such software).

References:

Pelz-Sharp, A. 2006, " ECM + WCM = ? " Retrieved 2. March, 2006

Robertson, J. 2006, "Grand enterprise projects: why are we wasting our time? " Retrieved 8. August, 2005

Comments

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...