Release Notes

Access control options

You can now configure access control for your docs at the project level to match how you share content with different audiences. Learn more in the Access Control documentation.

Access levels and example use cases

• Public — Make your entire documentation site visible to anyone.

  • Ideal for fully public product docs and API reference that should be discoverable by customers and search engines.

• Partial — Keep few docs public and few docs private.

  • Gate a few pages for internal teams such as Support, Success, or Sales while keeping the rest of your docs public.

• Private — Require authentication for all documentation.

  • Store internal code documentation, architecture notes, and engineering guides.

  • Centralize internal SOPs, runbooks, and operational checklists for on-call and support teams.

Documentation Templates

Choose from pre-built templates to customize the layout and style of your documentation site.

Available Templates

• Classic - Traditional documentation layout with a clean, focused reading experience. Ideal for technical documentation and API references.

• Atlas - Modern, visually rich layout with enhanced navigation and content presentation. Perfect for product documentation and user guides.

How to use

• Select templates from Settings → General → Brand & Theme in your dashboard

• Configure templates directly in your documentation.json file using the template property

• Further customize your selected template with colors, typography, branding, and navigation settings

Learn more in our Templates documentation.

The default docs domain is migrating from *.documentationai.io to *.documentatioai.com.

• Existing links automatically redirect; no action needed for most users.

• Update references only if you hard‑code the old domain in firewalls, allowlists, scripts, or integrations.

• Custom domains are unaffected and will continue to work as usual.

AI Documentation Agent (beta)

The AI Documentation agent is now available in beta for all workspaces. It helps you generate pages, apply rich visual components, and keep content aligned with your Documentation.AI configuration.

Where can you find it?

• Use the agent from the web editor (using "AI Agent" icon in the editor interface).

**What can you do today? **

• Draft new documentation pages from scratch or from short briefs.

• Make existing docs more visually appealing using rich components (Cards, Columns, Callouts, Tabs, Steps, and more).

• Generate and refine code samples or usage snippets for your APIs and SDKs.

• Use web search inside the agent to bring in up-to-date external information when needed.

Current limitations (beta)

• The agent is currently available only on the web. You can use coding agents like Cursor or GitHub Copilot if you are updating using an IDE.

• The agent understands Documentation.AI’s visual components and documentation structure, but does not yet take context from your codebases or support systems; these integrations are coming soon.

• The agent cannot yet run in the background or autonomously; background workflows are coming soon.

• All AI-generated content should be reviewed and edited before publishing

MCP Server for Your Docs

You can now expose your own documentation/knowledge as a Model Context Protocol server. This makes your published docs directly accessible to your end users, internal teams, and LLM‑powered tools.

Key capabilities

• MCP server for your docs is available by default when you publish your documentation

• Let end users, IDE agents, and chat assistants query your docs through an MCP endpoint you control

• Use structured page and API metadata to give agents more grounded and context‑aware responses

• Help product teams deliver LLM‑native support and troubleshooting experiences directly inside their apps