Pinned Tweet
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…
Get ready for next year’s State of Docs report: stateofdocs.com/2026/about
69
We asked a simple question about docs: Do AI coding agents actually read them?
Here’s what we found out.
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.
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
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
Content gaps are the expensive docs defect. Drift is the one you'll never hear about. We tested both on AI coding agents 👇
Docs Spotlight: How FreedomPay Turned Its Docs Into a Programmatic Handshake xitter.twitterapi.xyz/i/broadcasts/1AKEmvEPY…
2
361
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
A new quality layer for documentation: What's new in GitBook xitter.twitterapi.xyz/i/broadcasts/1mxPaZenL…
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
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
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
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.
Read the full post: gitbook.com/blog/documentati…
1
138















