GitBook
Documentation sites that stay in sync with your repository
GitBook publishes product documentation as a branded site, written in a block-based visual editor rather than by hand-rolling a static site generator. Content syncs both ways with GitHub or GitLab, so writers can work in the editor while engineers edit markdown in the repo and neither overwrites the other, and pull requests get preview deployments of the docs they change. API reference pages are generated from an OpenAPI spec with interactive playgrounds that let a reader send a request from the page. Paid plans add a custom domain, deeper branding, AI search, analytics and reader feedback; the top tier adds an AI assistant that answers from your docs and reports on what it was asked. Pages are optimised for language models as well as readers. Pricing is per published site plus a per-user fee for the team editing it.
- Block-based visual editor with custom blocks
- Two-way sync with GitHub or GitLab
- Preview deployments for documentation changes
- API reference generated from an OpenAPI spec
- Interactive playgrounds for sending requests
- AI search, and an AI assistant on the top tier
- Custom domain, branding and site redirects
- Analytics and reader feedback on paid plans
What people are saying about GitBook
50% neutral“I write on gitbook”
“- Moved our docs from @GitBookIO to @mintlify and saved $80/month. The”
“I recently started posting writeups on a github repo coz I wanted to maintain github contributiions streak but now I think using medium or gitbook would have been more sensible”
“i saw a guy's gitbook writeup profile and it's so clean and well maintain”