Component content management system
Lua error in package.lua at line 80: module 'strict' not found.
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] More often than not, the CCMS also contains the publishing engine to create the final outputs for print, web and e-readers.
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:
- Darwin Information Typing Architecture (DITA) (generic and adaptable)
- DocBook (generic)
- S1000D (defense, aerospace...)
- SCORM Shareable Content Object Reference Model (training and learning content)
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 (referential). 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 is typically used for multi-channel customer-facing content (marketing, usage, learning, support). The solution can be a separate system or be a functionality of another content management system type (for example, enterprise content management or web content management).
Compared to a "simple" management system, the CCMS tracks the files but also the collection of files. It tracks indirect and direct linking so that author can reuse safely content and check the applicability of changes.
Contents
Benefits
Benefits of managing contents at components level:
- Greater consistency and accuracy.
- Reduced maintenance costs.
- Reduced delivery costs.
- Reduced translation costs.[3]
- Traceability.
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.
Notes
- ↑ Howard Schwartz. "Why CCM is not a CMS: Or Why You Shouldn't Confuse a Whale and a Fish". The Center for Information-Development Management.
- ↑ "Crash Course for Content Management: What is content management?". Vasont Systems.
- ↑ Ann Rockley and Steve Manning. "Component content management: Overlooked by analysts; required by technical publications departments". The Rockley Group Inc.
Sources
- S1000D Official homepage
- OASIS Official DITA page
- Oasis Committee for DocBook
- SCORM
- Comparison of Document Markup Languages
External links
- DITA Best Practices: A Roadmap to Writing, Editing, and Architecting in DITA. Laura Bellamy, Michelle Carey, Jenifer Schlotfeldt. ISBN 0132480522 IBM Press (30 September 2011)
- DITA For Practitioners. Eliot Kimber.
- Introduction to DITA, 2nd Edition. JoAnn Hackos. ISBN 0977863433 Comtech Services, Inc (2011)
- DITA 101. Ann Rockley, Steve Manning, Charles Cooper. ISBN 0557072913 Lulu.com (3 July 2009)
- DITA Style Guide. [1]. Tony Self. ISBN 978-0-9828118-1-8 Scriptorium Publishing Services, Incorporated (24 February 2011)
