GitBook

Introducing GitBook's new quality monitoring layer. AI can help your team draft docs in minutes. How long does it take to find out one is wrong? That's why we're launching a new Improve section in GitBook, with 3 features that help you work on the quality of your docs as fast as you create them: Style guide - checks your pages against your own writing rules. Content gaps - shows you the questions your docs can't answer yet. Broken links - finds the links that go nowhere. Your team reviews every change before it's published, and we'll keep adding more checks. Currently available for Ultimate plan users in the app and through GitBook’s MCP.

FreedomPay's developer documentation used to live in PDFs and Confluence pages. Now it's what they call a programmatic handshake, connected over MCP and solid enough that the team built an app on top of it just to prove the docs held up. John Lueders, VP of Partner Technology at FreedomPay joins us to walk through the rebuild: what the old setup was costing them, the moment they decided to rip it out, and what they went looking for in a replacement. We'll also cover the migration itself, including what broke and what surprised them, the app they shipped to stress-test their own docs, and what has changed since launch, including how the team reacted and what they can now measure.

For API-first payments companies, the docs are the integration experience. That was John Lueders’ main focus for FreedomPay while migrating their developer docs. FreedomPay's payment platform operates in 88 countries, and its docs are the integration experience: they're what partners see before they talk to anyone. On October 27th, we’re going live with John to unpack how their team is getting the most out of GitBook. Save your spot: https://buff.ly/g0p4Ep9

Why is AI so much better at writing code than docs? Eric Holscher, co-founder of Write the Docs, has a great answer: a code pattern and a cliché are the same move. Leaning on what came before is good engineering and bad writing. He joined us on the latest State of Docs podcast to talk about what AI is doing to technical writing. He covered whether coding agents actually read your docs, the "context gardener" as a new kind of docs role, what the Write the Docs salary survey says about the profession, and why being visibly human is turning into an advantage. Watch the episode: https://lnkd.in/e8kMbSJ3

New episode of the State of Docs podcast! This time I spoke with Eric Holscher, co-founder of Write the Docs. It was great to catch up with him in person at WTD Berlin a couple of weeks back. As with many docs conversations today, a lot of this one was about AI - how it's affecting the job, the community, and the writing itself. Eric made a distinction that I found really useful: AI has gotten good at code faster than prose because code is easier to test against a right answer than writing is. A repeated pattern is good practice in code, but in writing it's a cliché. He's still optimistic, though. Now that everyone is writing prompts and working in text, the things tech writers are good at - specificity, translation, empathy for the user - matter more than ever. Write the Docs has done so much for the tech writing and documentation community, and it was a treat to have this conversation. Link in the comments.

A live walkthrough of everything we shipped recently, and where docs go next.

Agents now read our docs more than humans do. We have the analytics to prove it, and it changed what people are optimizing in their docs. They can't tell good docs from bad ones, so quality matters more now than it ever has. We've spent the last few months building tools that tell you what's missing, broken, or out of date in yours. We’re running a live session on October 1st around what we've shipped: Content gaps, broken links, style guide checks, and a rebuilt analytics view that separates agent traffic from human traffic. Save your spot here: https://buff.ly/T6QnQNi

It's the last day of Write the Docs Berlin! We've met so many great people from the docs community this week, and we're excited to keep those conversations going. If you haven't come said hi yet, find us before the day wraps.

Syncing your GitBook docs with a repo just got a major upgrade. Site-wide Git Sync is now available, which allows you to connect your entire site to a repository with a single configuration for every section and space. It also introduces gitbook-docs.yaml, so you can define and update your site's structure directly in your repo. Add sections, reorder pages, and reshape your navigation through a pull request. Setting it up or migrating your existing setup only takes a few seconds from your site's overview. Read more: https://buff.ly/ZCrEEji

Not all robots are the same. A search crawler indexing your docs is a robot. So is a vulnerability scanner. And so is ChatGPT pulling your API reference right now, because a real person just asked a question that depends on it. Most analytics put all of it in one bucket and call it bot traffic. If you publish with GitBook, your site insights already separate your traffic: which agents are reaching your docs, and what they're requesting. Read more: https://lnkd.in/eD33vTDN