Comments on: Building Your Requirements for a Content Management Implementation http://thecontentwrangler.com/2007/12/19/building_your_requirements_for_a_content_management_implementation/ Content is a business asset worthy of being managed Fri, 18 May 2012 01:51:49 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Fabrice Talbot http://thecontentwrangler.com/2007/12/19/building_your_requirements_for_a_content_management_implementation/comment-page-1/#comment-206 Fabrice Talbot Tue, 26 Feb 2008 03:10:15 +0000 http://localhost:8888/ee/?p=398#comment-206 <p>I agree with mots of the points. However I’d like to bring a worf of caution on “#4 - Plan an efficient workflow”. </p> <p> From experience, I would day that it is a bad idea to introduce a new content management workflow in your organization when you implement a CMS. Ideally the organization should already have a well-defined workflow process in place that can be mapped to the CMS. If not, get your new CMS up and running, get familiar with it, and then implement the workflow (usually possible ad-hoc since most CMS use worklfow engines). </p> <p> I would add “#7 - Usability”: pick a CMS that has a user-friendly UI and perhaps hide some of the complexity of XML (WYSIWYG UI). This can save a lot of pain inside the editorial team <img src="http://thecontentwrangler.com/images/smileys/grin.gif" width="19" height="19" alt="grin" style="border:0;" /> </p> <p> Fabrice </p> I agree with mots of the points. However I’d like to bring a worf of caution on “#4 – Plan an efficient workflow”.

From experience, I would day that it is a bad idea to introduce a new content management workflow in your organization when you implement a CMS. Ideally the organization should already have a well-defined workflow process in place that can be mapped to the CMS. If not, get your new CMS up and running, get familiar with it, and then implement the workflow (usually possible ad-hoc since most CMS use worklfow engines).

I would add “#7 – Usability”: pick a CMS that has a user-friendly UI and perhaps hide some of the complexity of XML (WYSIWYG UI). This can save a lot of pain inside the editorial team grin

Fabrice

]]>