How do I put this...?

I TOLD YOU SO!!!

From our report to the Technology Council, November 13, 2006:

Implementation and Migration

During system selection, the Task Force sought out software that was flexible, robust, but still simple enough to be used by non-technical end users. This was a critical lesson-learned following the attempted implementation of the Luminis CMS. The trade-off with this ease comes in the design, development, and migration of content.

For all systems examined, users generally fell into one of four categories:
• Administrator - what we traditionally consider the IT role of administering the server, application, database, and user account maintenance
• Content Creator (Designer) - the person who designs the aesthetic, lays out the navigation, and builds the actual templates
• Content Editor - anyone who: adds, removes, or changes content on a site, adds pages to an existing site, and adds a sub-site that uses existing templates
• Content Consumer - anyone who views the pages created in the CMS

While few webmasters currently have the skills to be Content Creators, these skills are only needed during design of a new site or redesign of an existing site. Irrespective of which system is chosen, training is available to bring someone up to the necessary skill level of a Content Creator. These skills, however, are not an abundant commodity.

The majority of what our webmasters currently do falls into the Content Editor category. For the sake of both efficiency and cost, it may make more sense to focus the design of templates and navigation in Web Communications and focus the webmasters into a Content Editor role, but with a greater responsibility of reporting on the state of content and maintaining workflows.

Migration of existing sites into either CMS was straightforward once templates were created. Participating departments will have the option of using predefined templates, or hiring Creative Services to customize one. Some departments may choose a third option: to pay an outside developer to create new templates.

May 3, 2007

Not done by Web Communications. After four weeks of training they had four weeks to play in test. This is their effort in production after 31 days ::




Done by Web Communications. They had the same training as the other group and just got their accounts in production three days ago ::