CMS (Content Management System)

If your DITA project involves large numbers of topics, many authors, or geographically distributed authoring and production teams, you may benefit from the features provided by a CMS, which can include:
  • Workflow support
  • Validation of topic links
  • Support for the Semantic Web
  • Localization (translation) support

To be truly effective, a CMS being used to store files for a DITA project must be aware of the tree-structued ("web") nature of the project, the content contained in the source files, and the relationships among the files and their content. The CMS must also be able to report on this kind of information: both meta information about the files, and syntactic and semantic information about the content. Ask your CMS vendor about the product's content analytical capabilities before deciding to buy.

It can also be useful for the CMS to include DITA Open Toolkit processing, and debugging and reporting aids that operate along with file processing. CMSs should also provide basic library (source control) functionality.

Popular CMSs include:
  • Hosted (web-based)
    • Astoria
    • DocZone
    • XDocs
  • Open-source
    • Alfresco
    • NetBeans
  • Proprietary, server-based
    • Documentum
    • Ixiasoft
    • Vasont
  • Hosted DITA training site: ditausers.org (includes the DITA Storm editor)
Related information
http://dita.xml.org/products-services
http://www.cmprofessionals.org