Documentation
Documentation people can use. A workspace teams can trust.
Author rich guides together, review changes in context, and publish a fast branded portal with search, API reference, versioning, and private access.
Authenticate every request
Use a scoped service token in the Authorization header.
Authorization: Bearer dtn_live_••••A documentation workflow the whole team can share.
Writing, review, delivery, and access controls belong to one product—not a loose chain of plugins.
Visual authoring and GitHub workflows
Live collaboration, comments, and review
Custom domains, private portals, and rollback
A real authoring workspace, not a repository-shaped text box.
Compose guides with code groups, tabs, diagrams, callouts, tables, embeds, and guided recipes. The visual editor and Git workflow resolve into the same structured content.
Work together in context
Presence, block comments, mentions, review requests, and external suggestions keep discussion beside the exact content it changes.
Preview the real release
Review navigation, authored pages, reference, examples, access rules, and custom branding before activation.
Know what readers need
Launch plans add reader analytics for pages, endpoints, entry paths, and search behavior.
One domain for human reading and agent discovery.
The published portal is the delivery surface. Human documentation, API search, and eligible agent-native files resolve from the same release instead of separate exports.
- Human portal
- /
- Agent context
- /llms.txt
- Read-only MCP
- /mcp
- Agent Skill
- /agent-skill.zip
Bring the useful structure with you.
Import a Markdown ZIP or public Git repository, preserve legacy redirects, and inspect what moved before the new domain becomes canonical.
Migration boundary
Public Git import supports GitHub, GitLab, and Bitbucket repositories. Live bidirectional runtime sync is currently GitHub only; arbitrary HTML site scraping is not offered.
Plan a migration ↗The portal stays connected to the work behind it.
Projects, permissions, revisions, and publishing history follow the content from draft to reader.
Dashboard
Writers, engineers, and product teams co-edit rich pages, discuss individual blocks, request review, preview, and publish.
GitHub and CLI
Keep docs in a repository workflow, or validate, pull, push, publish, and inspect release logs from the terminal.
MCP
Authenticated agents search the workspace, stage page changes, build previews, and publish only within project policy.
Know exactly what is live.
The active revision, served routes, and access boundary remain inspectable after the launch moment has passed.
- Immutable releases
- Every published portal points to an inspectable build. Rollback moves the pointer; it does not rewrite history.
- Access before bytes
- Private portal access is enforced at the edge before protected content is returned.
- Human and agent discovery
- Eligible public portals can serve search, llms.txt, read-only MCP, and Agent Skill download beside the human site.
Give the next developer one dependable place to start.
Import existing Markdown or a public repository, add your API model, and publish a portal the whole team can keep current.