Component content management system

From Wikipedia, the free encyclopedia
Jump to: navigation, search

A component content management system (CCMS) is a content management system that manages content at a granular level (component) rather than at the document level. Each component represents a single topic, concept or asset (for example an image, table, product description, a procedure).

The CCMS must be able to track "not only versions of topics and graphics but relationships among topics, graphics, maps, publications, and deliverables." [1]

Components can be as large as a chapter or as small as a definition or even a word. Components in multiple content assemblies (content types) can be viewed as components or as traditional documents.

Although modular documentation is not necessarily XML-based, it is usually the case. Standards include:

Challenges for the technical writers include topic-based authoring, that is shifting from writing book-shaped, linear documentation to writing modular, structured and reusable content component.

Each component is only stored one time in the content management system, providing a single, trusted source of content. These components are then reused (rather than copied and pasted) within a document or across multiple documents. This ensures that content is consistent across the entire documentation set.[2]

Each component has its own lifecycle (owner, version, approval, use) and can be tracked individually or as part of an assembly. Component content management (CCM) is typically used for multi-channel customer-facing content (marketing, usage, learning, support). CCM can be a separate system or be a functionality of another content management system type (for example, enterprise content management or web content management).


Benefits of managing contents at components level:

  1. Greater consistency and accuracy.
  2. Reduced maintenance costs.
  3. Reduced delivery costs.
  4. Reduced translation costs.[3]

Benefits of using a component content management system:

  • Version and control over the documents and the contents - reused or not.
  • Check impacts on reused content changes.
  • Improved collaboration and automation with workflows.
  • Manage documentation releases.
  • Ease of links and content maintenance.
  • Further reduce translation costs.
  • Higher collaboration.
  • Improved modularity.
  • Integration with editors.



External links[edit]