1. Implementing a Content Management System A Practical Guide

2. Web Services About Missouri State  Primary campus in Springfield with additional campuses in West Plains, Mountain Grove and China  Approximately 20,600 students  Over 200,000 web pages

3. Web Services CMS Defined A web content management system is used to manage and control a large, dynamic collection of web material (HTML documents and their associated images). A CMS facilitates document control, auditing, editing, and timeline management. A Web CMS provides the following key features:  Automated templates  Easily editable content  Workflow management http://en.wikipedia.org/wiki/Content_management_system

4. Web Services Administration Buy-In  Administration support is critical  Many cost factors involved in CMS  Software costs (may be mitigated by Open Source)  Personnel costs  University image/marketing costs

5. Web Services Necessary Timelines  Needs Analysis  Where are we and where do we want to be  Selection and Acquisition  Develop RFP and evaluate responses  Acquire selected product  Implementation  Install, training, rollout

6. Web Services Formation of Committees  Business Process Review Committee  Build a business case  Define Requirements  CMS Selection Committee  Develop RFP, review proposals, make recommendation  Implementation Committee

7. Web Services Types of CMS  Staged vs real-time  Component of larger system  Editor interface requirements  *User account authorization/setup

8. Web Services CMS Research  Education Related Networks  Listserv U-WebD  Conferences  Web Sites  CMS Matrix – www.cmsmatrix.orgwww.cmsmatrix.org  CMS Watch – www.cmswatch.comwww.cmswatch.com  Content Management Portal – www.contentmanager.net www.contentmanager.net  Open Source CMS – www.la-grange.net/cmswww.la-grange.net/cms  Reference checks for finalists

9. Web Services CMS Research  Costs – One-time vs ongoing  License structure  Administrator vs user  Negotiable  Sand box  Level of IT staff hand-holding of users  Training, open labs, etc.

10. Web Services Purchase and Implementation  Select and acquire product  Select and acquire hardware  Hire or reallocate personnel  Install  Initial training  Develop templates  Pilot project  User training

11. Web Services Staffing It’s a big software package so it runs on autopilot. Not!  Systems support  Expert designer  Training  Help desk

12. Web Services User Training  Critical to project success  Methodical and ongoing  Not everyone can attend an initial mass- training session  New adopters  New-to-campus users

13. Web Services Rollout Your method of rollout can help determine the results.  Isolated or large  Huge success  Visible failure  Little notice  Branding

14. Web Services Post-Implementation Benefits Gained  User-friendly, non-technical editing  Staged solution with workflow  Standard templates ensure accessibility and usability by computers, handhelds and other devices  Web-based; no external editor

15. Web Services Work That Remains  More departments to convert  Local extension and customization of CMS package  Ongoing monitoring of new technology and devices

16. Web Services Questions?  Questions  Comments

17. Web Services More Information  Brian Heaton Content Management Programmer/Analyst Web Services Missouri State University BrianHeaton@MissouriState.edu