A content management system (CMS) is a type of general-purpose documentation platform that splits the users into three communities: content producers, publishers, and readers. As such, CMS software is usually antithetical to DocOps principle of shared responsibility and offers poor adherence to most documentation system tenets except for the principles of uniform addressability and contextual wayfinding, subject to product support and appropriate configuration.
Some of the most popular CMS applications include:
| Name | OSS | Native Document Format | DocOps Automation |
|---|---|---|---|
| Adobe Experience Manager (AEM) | No | A subset of HTML wrapped in custom XML tags. | REST and GraphQL APIs, Java extensions (headless) and JavaScript. |
| Alfresco | Yes | HTML, Microsoft Word, and many others. | REST APIs and Java extensions. |
| Microsoft SharePoint | No | HTML, Microsoft Word, PDF, etc. | REST APIs, JavaScript, PowerShell/C# extensions, as well as high-level Power Automate, and SharePoint Workflows options. |
| Sitecore | No | A subset of HTML wrapped in custom XML tags. | REST APIs, C# and PowerShell extensions |
| WordPress | Yes | A subset of HTML interspersed with proprietary annotations. | REST API, XML-RPC API, and PHP |
In DocOps, CMS software is considered legacy software and an opportunity to plan and execute a migration to a more adequate documentation platform.
© 2022-2024 Ernesto Garbarino | Contact me at ernesto@garba.org