 Content management is a process and/or software application used by groups to plan, create, manage, store and distribute content.
 Content can include: web pages, images, documents, streaming media, news releases, etc.
 A CMS usually consists of a front-end editor for inputting content and a back end system for storing the content (usually a database).
 This content can then be formatted by a template and displayed in a variety of ways.

Content Providers
Top News,
School Communicators,
Etc.
Data
Entry
Form
Templates
Editor Content
Repository
 Content authors go on line to create and update their own sections of a collaborative publication (in our case the web site).
Accommodations are made for quality control by editorial staff and tools are provided for workflow management.

 Can facilitate sharing of content across multiple Web sites
 Can make it easier for non-technical staff to update content
 Forces a formal workflow management and publishing process
 Can improve consistency of look and feel

 Make editorial decisions for you.
 Decide or define what your workflow/approval process should be. You still need to set policy regarding who posts what and who needs approval from whom.
 Update many forms of media including pdfs, movies, flash, etc.


Support all the bells and whistles many of us are used to.
Doesn’t necessarily make it easier to update content.

 How widespread is the need for or interest in a CMS?
 What challenges will U.Va. face?
 How should we proceed?