Editing Content management (section)

==Process==
Content management practices and goals vary by mission and by organizational governance structure.
News organizations, [[e-commerce]] websites, and educational institutions all use content management, but in different ways. This leads to differences in terminology and in the names and number of steps in the process.

For example, some digital content is created by one or more authors. Over time that content may be edited. One or more individuals may provide some editorial oversight, approving the content for publication.

[[Publishing]] may take many forms: it may be the act of "pushing" content out to others, or simply granting digital access rights to certain content to one or more individuals. Later that content may be superseded by another version of the content and thus retired or removed from use (as when this wiki page is modified).

Content management is an inherently collaborative process. It often consists of the following basic roles and responsibilities:

* '''Creator''' – responsible for creating and editing content.
* '''Editor''' – responsible for tuning the content message and the style of delivery, including translation and localization.
* '''Publisher''' – responsible for releasing the content for use.
* '''Administrator''' – responsible for managing access permissions to folders, collections and files, usually accomplished by assigning access rights to user groups or roles. Admins may also assist and support users in various ways.
* '''Consumer, viewer or guest''' – the person who reads or otherwise consumes the content after it is published or shared.

A critical aspect of content management is the ability to manage versions of content as it evolves (''see also'' [[version control]]). Authors and editors often need to restore older versions of edited products due to a process failure or an undesirable series of edits. Time-sensitive content may also require updates as the subject matter evolves over time.

Another equally important aspect of content management involves the creation, maintenance, and application of review standards. Each member of the content creation and review process has a unique role and set of responsibilities in the development or publication of the content. Each review team member requires clear and concise review standards. These must be maintained on an ongoing basis to ensure the long-term consistency and health of the [[knowledge base]].

A content management system is a set of automated processes that may support the following features:

* Import and creation of documents and multimedia material
* Identification of all key users and their roles
* The ability to assign roles and responsibilities to different instances of content categories or types
* Definition of workflow tasks often coupled with messaging so that content managers are alerted to changes in content
* The ability to track and manage multiple versions of a single instance of content
* The ability to publish the content to a repository to support access
* The ability to personalize content based on a set of rules

Increasingly, the repository is an inherent part of the system, and incorporates [[enterprise search]] and retrieval. Content management systems take the following forms:

* [[Web content management system]]—[[software]] for [[web site]] management (often what ''content management'' implicitly means)
* Output of a [[newspaper]] editorial staff organization
* [[Workflow]] for [[essay|article]] publication
* [[Document management system]]s
* [[Knowledge management software]]
* [[Single source publishing|Single source]] content management system—content stored in chunks within a relational database
* Variant management system—where personnel tag source content (usually text and graphics) to represent variants stored as single source "master" content modules, resolved to the desired variant at publication (for example: automobile owners manual content for 12 model years stored as single master content files and "called" by model year as needed)—often used in concert with database chunk storage (see above) for large content objects