Trawling for advice on Vignette

vignette.gifI recently had the need to get information on Vignette (story server) in a hurry, and followed a certain methodology which is no doubt common to many.

In order:

  1. Google
  2. Vignette’s site
  3. Wikipedia
  4. Phone dev friends
  5. Twitter
  6. Post a question on LinkedIn

You could seperate the first 3 into old-style information harvesting (even wikipedia), #4 into common sense, and #5 and #6 into “leveraging social media”. Well, the winner by a country mile for answers was LinkedIn! Let me share with you those that were public answers:

Vignette server: difficult to develop a website on top of it or not?


Krishna Kumar: Sr. Vice President & Group Editor – DARE at CyberMedia India Ltd
If you are talking fo getting it done by a consultant, that can be costly.

And the cost may have nothing to do with the complexity.

Vignette is supposed to be one of the most scalael and highend content servers out there, having hosted sites for Olympics, etc.

The server (plus various additional modules) itself is very costly. And consultants with experience on vignette do not come cheap


Eric Small: Director, Consumer Product, with extensive technology background, focus on web communities and UGC
If you’re at the point you’re even asking this question, you’ve got a difficult task ahead of you. Vignette, or any enterprise-level CMS, is meant to solve the problem of large-scale content management. By and large, when you get to this point, your web site is going to be complex (and thus difficult). Otherwise you wouldn’t be considering spending that much $$$.

Use the CMS Watch report at to make sure you’re getting the right vendor. And get someone in your organization to read the CMS Bible by Boiko (ISBN 978-0764573712) to get a good sense of the process of building out a CMS-driven system. If you have the leverage (and you should with this kind of investment) insist on a prototype before signing on the dotted line.

By the way, if all of this seems out-of-scale for what you’re doing, you probably shouldn’t be looking at Vignette. For smaller implementations there are good open-source solutions like Drupal and OpenCMS.

Luis Mendez: Solutions Architect
Vignette can be very complex. But this will be the case with any combination of portal server, web server, application server, content management server, and dynamic business objects delivering along with search, security, and high performance environment.

It really depends on how you want to foray into the Vignette products themselves.

On one hand, you can use the Vignette out of the box content managers and have everything sent out via RSS, XML and so forth. That’s easy assuming all content management is done through the apps that come preconfigured out of the box.

On the other hand, doing things like delivering secured data with integrated directories and other ACLs on both the content management and the content delivery is another bowl of wax.

There are of course other issues to deal with such as client side request through frameworks like AJAX, how portlets communicate with one another in multiple states and how all of that translates into where you content is going to come from.

Getting a Vignette consultant on board would be an expensive proposition because they can help you traverse all of these topics. They are typically well versed in all areas of the web and then some!

What did we learn? That LinkedIn is powerful as it filters a lot of the noise and is targeted at professionals,  that you will get an answer from strangers and friends alike and that anyone wanting hard skills in this economy should hit the Vignette books. Thanks all!

About Derek

My key interests are online investor relations, websites, social media, enterprise 2.0 and intranets, and XBRL. Speak to me if you need a solution in any of these disciplines, or follow my knowledge links on this site and others. Find me on Twitter, LinkedIn or in recent conversations.

Comments are closed.