This is a (very) short list of tools and platforms to create Documentation. I divide documentation tools into the following groups:
- Static Site Generators (SSG)
- SaaS Documentation Platforms
- Self-Hosted Dynamic Documentation Platforms (Wikis)
- Help Authoring Tools (HATs)
- Component Content Management Systems (CCMS)
Static Site Generators (SSG)
Tools that generate a static HTML/CSS/JS website from Markdown (or similar). Content lives in Git, and you host the site yourself. For more information, see Static Site Generators. Ideal for: Developer documentation, versioned docs, Git workflows, fast static hosting.
Key Features:
- Write Markdown or similar files.
- Build static HTML/CSS/JS.
- Host the output anywhere (GitHub Pages, Netlify, S3).
Examples:
SSGs that I havn’t checked out yet: Retype
SaaS Documentation Platforms
Fully hosted, cloud-based solutions with web UIs and built-in collaboration. Ideal for: Teams who want zero maintenance, built-in collaboration, and don’t mind paying subscription fees.
Key Features:
- Fully hosted by the vendor.
- Web-based editors.
- No infrastructure or servers to maintain.
Examples:
Self-Hosted Dynamic Documentation Platforms (Wikis)
Open-source tools you install yourself. Content stored in a database, dynamic page generation, built-in permissions. Ideal for: Organizations who want full control and on-premise hosting.
Features:
- Install and maintain the server.
- Dynamic content stored in a database.
- Web UI for editing and permissions.
Examples:
Help Authoring Tools (HATs)
Desktop software for producing help files (CHM, HTML Help, PDFs) and manuals. Ideal for: Software user guides, context-sensitive help systems, offline documentation.
Examples:
- HelpSmith – Windows app for CHM, Web Help, PDF.
- Help+Manual – Versatile help authoring, many export formats.
- Adobe RoboHelp – Industry-standard, commercial solution.
- Doc-O-Matic – Documentation generator for developers.
Also refer to # 10 Best RoboHelp Alternatives and Competitors for 2025
Component Content Management Systems (CCMS)
Enterprise-grade tools for modular, structured content creation and multi-channel publishing. Ideal for: Large organizations where you need to use structured authoring (DITA XML, DocBook, or proprietary XML), reuse content modules across multiple outputs, manage translations and variants and/or deliver multi-channel outputs (HTML5, PDF, Help, ePub, etc.).
Examples:
- Paligo (SaaS)
- SCHEMA ST4 (Self-hosted / On-premise)
- Tridion Docs
- Author-it
- MadCap IXIA CCMS
Comparisson
DISCLAIMER: The following overview was generated by ChatGPT:
| Static Site Generators (SSG) | SaaS Documentation Platforms | Self-Hosted Wikis | Help Authoring Tools (HATs) | CCMS / Structured Authoring | |
|---|---|---|---|---|---|
| Primary Use Case | Public docs, developer guides, product sites | Internal/external knowledge bases, collaboration | Internal knowledge base, internal wiki | Software help files, manuals, offline help | Enterprise modular content reuse, multi-channel publishing |
| Content Storage | Files in Git repos (Markdown, reStructuredText) | Cloud database | SQL DB or flat files | Proprietary project files | Structured XML (DITA, DocBook, or proprietary) |
| Editing | Markdown in text editor, Git workflows | Web-based WYSIWYG and Markdown editors | Web-based WYSIWYG and Markdown editors | Desktop WYSIWYG editors | Structured XML authoring, often in proprietary editors |
| Hosting | Self-hosted (static web server) | SaaS cloud platform (hosted for you) | Self-hosted server (Node.js, PHP, etc.) | Local machine output generation | SaaS (Paligo) or on-premise (SCHEMA ST4) |
| Versioning | Git-based | Built-in version history | Built-in revisions | Project-based, versions managed locally | Granular versioning per component/module |
| Output Formats | Static HTML | Static/dynamic web portal | Dynamic web portal | CHM, Web Help, PDF, ePub | HTML5, PDF, Web Help, Word, InDesign, ePub |
| Collaboration | Git workflows, pull requests | Multi-user, real-time collaboration | Multi-user with permissions | Limited collaboration (single-user focus) | Enterprise workflows, roles, translation workflows |
| Content Reuse | Limited (snippets, includes) | Some support (templates, snippets) | Limited (page templates) | Medium (topics reused across outputs) | Very high (modular components, variants, reuse mapping) |
| Translation Support | Manual (separate files or branches) | Often built-in or via integrations | Limited to none | Manual or via export | Fully integrated translation workflows |
| Authentication | Usually public or simple protected hosting | Built-in authentication & SSO options | LDAP, SAML, OAuth integrations | N/A (output consumed elsewhere) | Enterprise SSO/LDAP integration |
| Ease of Use | Developer-friendly, steep learning curve | Very user-friendly for non-technical users | Moderate—technical setup but easy editing | Familiar Windows UI, technical learning curve | Complex, requires training |
| Typical Users | Developers, tech writers comfortable with Git | Business teams, support teams, product teams | IT teams, internal knowledge management | Technical writers producing software help | Enterprise documentation teams, regulated industries |
| Cost | Free/open-source | Subscription-based SaaS | Free/open-source or low-cost hosting | Commercial licenses | High enterprise licensing costs |