It seems Chris Summer’s revelations about the new Workflow have started some nice discussions. A lot of people want to give workflow a proper chance and meaning in the workflow discussions and implementations.
Just to make my point I’d like to work with images. Looking at the main image of this post is what everyone hopes workflow will do to their content flow in the organization. Making every piece of content go into the appropriate lane and reach the destination without delay.
But, a workflow implementation can very easily cause the opposite (see image below). Content is waiting for actions by someone, which can easily become a big
traffic jam of content. At this point solving the jam is more important than editing and reviewing each piece of content. This is usually the moment Workflow “temporarily” gets disabled or simplified.
Anyway, the future brings new hope! Now read some of the other blogs posted about Workflow:
- Will bundles be the saviour of Tridion workflow?
- Aint Got No (SDL Tridion) Workflow… Blues?
- Why we don’t use SDL Tridion Workflow
- Workflow Dreamin’
After the Tridion Community Webinar of march 14th 2012 one of the main topics was about navigation. An example was shown of creating a navigation based on Taxonomy by Chris Summers, but of course, and I re-quote:
"Essentially, as a wise man once noted, there are as many ways of rendering navigation as there are Tridion Consultants"
So Mark Saunders want to get the debate started on how you (Now, imagine Uncle Sam pointing his finger at you) make your navigation. Join the discussion at the Joined Tridion Developer blog tridiondevelopers.com!
For those of you who have missed the Tridion Community Webinar on March 14th….