GitBook (@GitBookIO) header
GitBook (@GitBookIO) profile picture

The docs platform for technical teams and AI agents

San Francisco
Joined April 2014
Photo by GitBook (@GitBookIO)Photo by GitBook (@GitBookIO)Photo by GitBook (@GitBookIO)Photo by GitBook (@GitBookIO)Photo by GitBook (@GitBookIO)Photo by GitBook (@GitBookIO)Photo by GitBook (@GitBookIO)Photo by GitBook (@GitBookIO)Photo by GitBook (@GitBookIO)Photo by GitBook (@GitBookIO)
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.
1
12
915
London! We’re back next week for @writethedocs 🇬🇧 Expect pizza, good company and plenty to see. I'll give a behind-the-scenes look at how we run our own docs on GitBook, and we'll talk about State of Docs too. Grab your spot here: meetup.com/write-the-docs-lo…
1
1
1
5
423
We asked a simple question about docs: Do AI coding agents actually read them? Here’s what we found out.
15
2
3
9
824
As promised, now that the security incident is resolved, we’ve published our post-mortem. You can read it here: gitbook.com/status/security-…. Apologies again for this disruption, and thank you everyone for your patience.
1
1
3
328
We can confirm that the security incident that occurred on November 2 is now resolved. We’ve restored functionality across the GitBook platform. A post-mortem will be shared shortly for insights and learnings here: buff.ly/EFgktAE Thank you for your patience.
3
298
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
1
3
2
1,228
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
4
1
6
7
3,143
Content gaps are the expensive docs defect. Drift is the one you'll never hear about. We tested both on AI coding agents 👇
6
2
10
1,679
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
3
5
337
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.
1
4
337
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: youtube.com/watch?v=Fj80Kl5d…
1
3
270
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.
1
1
301
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…
3
278
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…
2
285
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…
2
284
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
1
2
2
367
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
1
2
140
Improving your docs and advocating for them are two different jobs — and they need different metrics. We wrote about which numbers to fix your docs with, and which to bring to leadership.
1
1
5
370
Your coding agent is already writing your docs. Now it can leverage GitBook too. Skills for authoring GitBook-flavored Markdown, configuring sites, creating change requests — and even reviewing them, just by asking. npx skills add GitbookIO/gitbook-skills
2
4
301