Syncing your GitBook docs with a repo just got a major upgrade.
Site-wide Git Sync connects your entire site to a repo with a single configuration. And the new gitbook-docs.yaml lets you define your site's structure in code, so navigation changes ship through a PR.
The GitBook app, the GitBook API, and published docs are available again. A few services may still be degraded as we finish restoring everything to full performance.
More information: buff.ly/MMW5WpP
Live updates: buff.ly/W5RMqPw
We’re addressing a security incident affecting GitBook. Some services are temporarily offline while our team restores them safely.
More information: gitbook.com/status/security-…
Live updates: status.gitbook.com
We just launched something new: @GitBookIO Research
We host docs for thousands of teams, which gives us a rare view of how documentation actually gets read — by people and, more and more, by AI.
The GitBook team got together for our semiannual offsite in Ibiza last week.
As our remote-first team grows, the in-person time we get as a team is more important than ever. We had lots of great conversations, saw some amazing demos, and aligned on what’s next for the future of knowledge, GitBook, and documentation as a whole.
Interested in joining for our next offsite? We’re hiring!
Explore our open roles: gitbook.com/careers
For API-first payments companies, the docs are the integration experience. That was the main focus for FreedomPay while migrating their developer docs.
On October 27th, we’re going live with their team to unpack how they’re getting the most out of GitBook.
Why is AI so much better at writing code than docs?
@ericholscher's answer: a code pattern and a cliché are the same move. Reusing what came before is good engineering and bad writing.
He joined us on the latest State of Docs podcast: piped.video/watch?v=Fj80Kl5d…
Agents read our docs more than humans do. They can't tell good from bad, so quality matters more than ever.
We built tools that find what's missing, broken, or out of date. Join us on October 1st to see it all in action.
Syncing your GitBook docs with a repo just got a major upgrade.
Site-wide Git Sync connects your entire site to a repo with a single configuration. And the new gitbook-docs.yaml lets you define your site's structure in code, so navigation changes ship through a PR.
Not all robots are the same.
Some of your "bot traffic" is scanners you should block. Some of it is standing in for a person who needs exactly what you wrote.
GitBook gives you the full picture for your site’s traffic, automatically.
Read more: gitbook.com/blog/bot-traffic…
We're heading to Write the Docs Berlin next week! 🇩🇪
Come find the GitBook booth on the 7th and 8th. We want to hear what's working in your docs and what's quietly driving you up the wall.
Register here: writethedocs.org/conf/berlin…
Moving your docs shouldn't be a one-person job.
GitBook Agent can now import your existing docs — give it the URL of your current site and it pulls everything into a change request ready to review.
gitbook.com/docs/changelog#i…
Super excited for the swag we’ve been cooking up for @GitBookIO this year 👀
Come meet me and the team at one of our upcoming events and we’ll give you some!
Register at gitbook.com/events
Docs aren't just where users go for answers anymore. They're the knowledge infrastructure your users and their AI agents depend on.
We've been tracking the shift for years. State of Docs 2026 is live: stateofdocs.com/2026
Wondering if your own docs are agent-ready? We built two free tools:
Agent Score — see how well agents can reach and parse your docs: gitbook.com/agent-score
Skill Generator — turn your docs into a SKILL.md for Claude, Cursor, Codex + 30 more: gitbook.com/skill-generator