Transcript Successful WCMS Implementation - CSU Web Services

A Successful Web Content
Management System
Implementation
Jay Knape
Manager of Web Services
Columbus State University
Successful WCMS Implementation
Successful WCMS Implementation

Success


In the first 14 months, the Web Team
has implemented 62 (50%) of CSU
sites into OmniUpdate OU Campus.
All done by:
3 full time staff
 Up to 4 student assistants

Successful WCMS Implementation
Redesign of Web Pages
____________________________
CMS Implementation
Successful WCMS Implementation

Why Split?

Best Practice



Dos and Don’ts of implementing a WCMS
Focus on task at hand
Learning curve for WCMS
Successful WCMS Implementation

Where we started


September 2006
Finalized 6 layouts
Successful WCMS Implementation



Implemented new look with existing
tools
December 2006 – RFP for WCMS
May 2007 – Reward RFP to
OmniUpdate
Successful WCMS Implementation


August 2007 – Installed and
Configured OmniUpdate
As of October 2007

51 sites were in the new look


38% of sites selected to move into
OmniUpdate
134 total site within colstate.edu
domain

28% sites would not moved into WCMS
Successful WCMS Implementation

Process



Student Assistants
 Worked on sites already in new look
Staff
 Continued working with departments doing
complete redesign
Sites
 Only active pages
 HTML 4.0 W3C standard
 508 accessibility guidelines
 CSS styling
Successful WCMS Implementation

October 2008


77 sites in WCMS
 15 sites in development
 62 sites live
 44,630 files
 3,173 directories
145 Users trained
 Trainer – Jay Knape
 1.5 hour training class
 Required class
Successful WCMS Implementation

Changes made:





Windows to Gentoo Linux
IIS to Apache
ASP to PHP
MS SQL/Access to MySQL
MS Frontpage to Dreamweaver
Successful WCMS Implementation

Encounters

Redesign
Everyone wants to be on the University
home page
 Welcome attitude for the layouts
 “Do I have to look like everyone else”
attitude

Successful WCMS Implementation

Encounters

WCMS
ASP on Apache
 Quirks with OmniUpdate
 Getting the templates set-up correctly

A Successful Web Content
Management System
Implementation
Jay Knape
[email protected]
Manager of Web Services
Columbus State University