190 likes | 313 Views
Implementing a Content Management System. A Practical Guide. 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. CMS Defined.
E N D
Implementing a Content Management System A Practical Guide
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
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
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
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
Formation of Committees • Business Process Review Committee • Build a business case • Define Requirements • CMS Selection Committee • Develop RFP, review proposals, make recommendation • Implementation Committee
Types of CMS • Staged vs real-time • Component of larger system • Editor interface requirements • *User account authorization/setup
CMS Research • Education Related Networks • Listserv U-WebD • Conferences • Web Sites • CMS Matrix – www.cmsmatrix.org • CMS Watch – www.cmswatch.com • Content Management Portal – www.contentmanager.net • Open Source CMS – www.la-grange.net/cms • Reference checks for finalists
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.
Purchase and Implementation • Select and acquire product • Select and acquire hardware • Hire or reallocate personnel • Install • Initial training • Develop templates • Pilot project • User training
Staffing It’s a big software package so it runs on autopilot. Not! • Systems support • Expert designer • Training • Help desk
User Training • Critical to project success • Methodical and ongoing • Not everyone can attend an initial mass-training session • New adopters • New-to-campus users
Rollout Your method of rollout can help determine the results. • Isolated or large • Huge success • Visible failure • Little notice • Branding
Post-ImplementationBenefits 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
Work That Remains • More departments to convert • Local extension and customization of CMS package • Ongoing monitoring of new technology and devices
Questions? • Questions • Comments
More Information • Brian HeatonContent Management Programmer/AnalystWeb ServicesMissouri State UniversityBrianHeaton@MissouriState.edu