Off the Bit
Tools: Docs and content
Category: Catalogue
Count: 31 catalogued, 1 not answering
Docs and content
Documentation platforms, headless CMS and localisation.
31 tools, described from their own homepages and last
checked 2026-09-04. 1 of those homepages did not answer. None of them is used to build this site. A row is a description, not an endorsement.
All 31
Alphabetical. Checked on 2026-09-04; anything that did not answer says so.
- API design, mocking, testing and documentation in one desktop tool, generated from requests you have already made.The four API tools, collapsed into one.
- Publishes API documentation from OpenAPI, with change detection between versions and MCP servers generated alongside.Treats a spec change as an event worth announcing.
- A headless CMS built for many channels at once, now positioning content as something agents consume as well as browsers.Content as an API, from before that was obvious.
- A headless CMS with a strong editorial interface and a GraphQL API built for performance budgets.Built for the editor as much as the developer.
- Hosted documentation for product docs, knowledge bases and API reference.Documentation hosting without building a site.
- Generates architecture and sequence diagrams from a text description, from the Eraser team.Diagrams without opening a drawing tool.
- Meta's React documentation site generator, with versioning and search built in.The default for open-source docs, largely by being there first.
- Generates structured documentation for a whole codebase from the repository itself.Documents what is there, not what was intended.
- Generates SDKs and documentation from an API specification, so client libraries are output rather than maintenance.The SDK stops being a repository somebody owns.
- Open-source publishing with newsletters and paid subscriptions built in, run by a non-profit foundation.The blog that comes with a business model.
- A documentation platform with docs-as-code support that also answers user questions and reports what is missing.Reports the gaps as well as hosting the pages.
- GitBook AI the page returns 404GitBook's AI features, listed as a separate product. That page now returns 404.Folded into the main product.
- A VS Code extension that explains code rather than writing it, aimed at reading unfamiliar sources.Explains instead of generating, which is rarer.
- Localisation engines that hold glossaries, brand voice and per-locale model choices, callable from code or CI.Translation memory, rebuilt around models.
- Translation automation that keeps context and leaves final quality decisions with people.Automates the drafting, not the sign-off.
- Continuous localisation from the authors of i18next, keeping translation in step with the code that uses it.Built by the people who wrote the library underneath it.
- Open-source outliner storing notes as plain files on your disk, with a graph built over them.Your notes stay files, which is the whole point.
- Documentation hosting that keeps pages in step with the codebase, now aimed as much at agents reading docs as at people.Docs as a retrieval surface, not a website.
- Documents, databases and wikis in one workspace, now with agents that act on the contents.Replaced four tools by being adequate at all of them.
- A local-first notes application over plain Markdown files, with linking and a plugin ecosystem.Files on disk, which is why people trust it.
- Hosted API reference documentation with a console readers can call endpoints from.Documentation you can send a request from.
- Generates a README from a repository, covering the projects that never got one.Writes the file everyone skips.
- Codebase intelligence: health scores, generated documentation, dead code detection and architectural history.Reports on the codebase rather than editing it.
- A headless CMS that treats content as structured data with a query language, rather than as documents.Content as a queryable dataset.
- A team knowledge base built for readability, with integrations into the tools the content refers to.Optimised for the person reading it later.
- Began with SDK generation from API specifications, now positioned around governing agents and MCP servers.Moved from SDKs to the agent control plane.
- A local-first knowledge graph and retrieval store for agent memory, built on a published pattern.Memory that stays on the machine.
- Documentation coupled to the code it describes, so a change that invalidates a document is caught in CI. Now aimed at legacy modernisation.Fails the build when the docs go stale.
- API documentation built for people and agents together, with private portals, changelogs and MCP output.Publishes for the agent as well as the reader.
- Open-source localisation with in-app translation, so strings are edited where they appear.Translate in place, not in a spreadsheet.
- An open-source documentation framework with themes, OpenAPI and GraphQL support and a plugin system.Docs framework with no configuration ceremony.
Other shelves
115AI assistants and agents 88Workflow and productivity 66Testing and code quality 45Security and secrets 41Models and AI infrastructure 41Monitoring and analytics 35Data, APIs and backends 34CI, CD and infrastructure 29Payments and messaging 22Hosting and cloud 18Terminal and CLI 16Design and media 10Editors and IDEs
ImranTools[Docs and content]