PUBLIC DOCS
You
Create, collaborate, and publish public docs on a platform built to keep your product knowledge accurate, AI-ready, and easy for users to find. Used by 150,000 startups, enterprises, and open-source projects.
One workflow.
Many ways of working.
FAQs
What are public docs?
Public docs are documentation that anyone can access online without signing in. Teams use them for product guides, developer documentation, API references, onboarding, and technical support.
What should a public documentation platform include?
A strong public documentation platform should support collaborative writing and reviews, technical content such as Markdown and code, searchable publishing, developer workflows, customization, analytics, and tools for keeping content accurate over time. GitBook brings these workflows together while also making published knowledge useful to AI.
Can GitBook be used for developer documentation?
Yes. GitBook supports technical and developer documentation with Markdown, Git-based workflows, code blocks, OpenAPI-powered API references, integrations, and AI tools for writing and maintenance.
Does GitBook optimize public docs for AI?
GitBook makes published content accessible through AI-friendly formats and connections such as MCP and llms.txt, while GitBook Agent helps teams identify missing or outdated source content.
Can users ask questions instead of searching through GitBook docs?
Yes. GitBook Assistant lets users ask questions and receive contextual answers grounded in your product knowledge, so they don’t always need to manually browse or search through documentation pages.
You can also embed GitBook Assistant into your product, marketing site, or anywhere else your customers would benefit from product knowledge.
