From Vignette to OpenCMS

Based on a recent project for redeveloping a Vignette based site using OpenCMS, here are some observations:

OpenCMS is infinitely extensible even though it takes some time to figure out things. So, though there were technical challenges, all of them were sorted out.
One major area in which OpenCMS (and other open source products) lags behind Vignette (and other proprietary products) is the ability to replicate content. This has the following implications:

1. You cannot have a separate environment for content staging and content delivery. This basically means that when content people publish stuff, it remains on the same system. It just moves from an offline project to an online project. In my opinion, the requirements for a staging environment and a production environment are (and should be) completely different. For example, you might want to cache articles on a live site but you wouldn’t want to cache them on a staging site. Similarly, a production environment could have a different load balancing and clustering strategy than a staging environment.

2. There are cases when your CMS integrates with third party applications. So for example, you get data from a third party feed, process it, take it thru workflow and publish it to the live environment. If both the staging and live are same and something goes wrong with the staging environment, the live site too goes down. Not a desirable situation at all!

3. One of the major benefits of a content management system is that you can repurpose content. For example, you create content centrally but publish it to different sites which could be dispersed geographically.

4. Since there is no replication, it becomes difficult to cluster and scale up. OpenCMS does provide an add-on module for clustering but most others do not.

5. Taking site back ups (as opposed to database backup and file system backup) is tricky.

However, most SMEs do not require such capabilities and as Alan points out here that if you are an SME, you need not go for the big vendors.

In such scenarios, we also use this opportunity to do a content assessment and often face challenges that are much more complex than technology challenges. This highlights the importance of softer issues in implementing CMS solutions. Some of these are:

1. There are a lots of pages which are not being used at all. However, their owners are reluctant to drop those pages – they get emotionally attached! So it is a tough task to get a final list of pages to be implemented.

2. Until now, people have been used to doing things in a particular way using the older system. So it takes a lot of effort to train them and make them comfortable with the new system. In my opinion, it is more of an intertia or resistance to change that make it difficult for them.

3. I’ve often heard “The previous system had this but the new system does not have this” type of statements. I believe when one buys a product, one not only gets the advantages but also the limitations. So sometimes it is not possible to do things as they were done by the previous system and the only way to sort this out is by training and hand holding.

However, in this case, OpenCMS has been a very good choice and the client has been very satisfied with the fact that we’ve been able to implement all the required features. If a large bank can choose Open Source, it certainly is becoming a viable alternative.

6 thoughts on “From Vignette to OpenCMS”

  1. Base on my 10+ years experience working with various Content Management Systems (CMS) and 6 months using Vignette I can affirm that Vignette is THE worst CMS I have ever worked with.

    I’m working for a large respected Canadian organization and we are very unhappy with Vignette. We are switching to another CMS. I won’t tell the name of the new CMS or the organization. I’m expressing my personal opinion here. And I don’t want to make publicity for the other tool before trying it.

    Here are some naked facts about Vignette:

    – Their tech support is poor and slow. They aren’t able to fix simple Vignette bugs.

    – Very expensive in our case $250,000 to $500,000 so far and growing.

    – Vignette is mostly a Consultingware: A CMS first developed for a limited number of consulting clients, then hastily rebranded as a “product” matching everybody needs. The fact is it doesn’t match OUR needs.

    – Counter-productive tool for employees. Awful workflow.

    – Poor documentation & support from Vignette.

    – Steep learning curve. Complicated interface.

    – Security features are dangerously weak. Easy for concurrents to access sensitive information. A friend of mine is testing security features as a living to prevent hacking, according to his testing it takes less than 5 minutes to hack Vignette and access sensitive information.

    PRO: Sales team.

  2. I put “Sales team” in PRO to make a sarcastic joke. Their sales team are very good at telling LIES and DECEIVED the client.

Comments are closed.

If you would like to get short takes directly in your mailbox, please do consider subscribing to my newsletter. I won’t spam you and your information will be safe. I usually send it like once a week (or once in 15 days).

%d bloggers like this: