GitBook

The number 1 challenge product teams told us they have with docs? Keeping them up to date with product changes. Docs fall behind because updating them means context-switching. You're mid-sprint, something ships, and updating the docs is a task for later — and sometimes later never comes. GitBook Channels brings documentation into the tools your team already works in. Kicking off a change request is as easy as mentioning @GitBook in a thread. We're running a webinar on June 23rd to show you how it works. Register here: https://lnkd.in/ews7M2ac

AI changes who reads your docs. It doesn't change who they're for. Sarah D. makes the case that even when agents retrieve, summarize, and execute your documentation — there's always a human on the other side of the outcome. Read the full post: https://lnkd.in/eNJ33ibD

GitBook Agent just got a lot more embedded in the editing experience. You can now open it directly from the editor via a new floating panel — no sidebar needed. Spot something that needs updating? It handles it inline, right where you're working. And if you're on a free plan: you can now try Agent too, with a soft weekly limit that resets automatically. Read more in the changelog: https://lnkd.in/eH7VYzit

"Information architecture will always matter." CT Smith at Payabli put it bluntly — even after finding that 68% of their users went straight to search and nobody touched the table of contents. Nearly 70% of documentation teams now factor AI into their information architecture and docs decisions. Structure isn't just a “nice-to-have” anymore. Interested in contributing to next year's report? Get in touch: https://lnkd.in/ezqrb2e2

GitBook Agent improvements, better filtering for AI insights, and updates to the editing experience for you and your team. See everything we shipped this month in our May roundup: https://buff.ly/yXPMVZR

Gamma uses GitBook to power their developer docs — serving fast, clean, and up-to-date information to LLMs and their users. Learn why hundreds of teams trust GitBook for documentation that's ready for AI: https://lnkd.in/gt-ZEcK9

Most teams spend a lot of time on the words in their docs, and not much time on anything else. But structure, hierarchy, and visual consistency have a real effect on whether readers trust your docs, find what they need, and come back. We put together 5 concrete things that consistently make the biggest difference — from getting your information architecture right before touching the customization panel, to why landing pages should always be built last. https://lnkd.in/gVWbD5Kb

Agent-ready docs doesn't only mean having an MCP server. It also means having SKILL.md file — Markdown that tells agents how to actually use your product. We broke down the difference between the two, and how teams are combining them to build docs that AI agents can actually act on. https://lnkd.in/gegmfDk5

Most documentation rewrites fail because teams migrate the mess instead of fixing it. Frends did something different — they scrapped everything and rebuilt from scratch on GitBook. Instead of documenting every edge case, write enough for your AI assistant to truly understand the product, and let it guide users from there. As Mikko Sairo puts it: “The documentation writing process turned from creating the perfect set of documentation to something closer to teaching the AI our product." Read the full story: https://lnkd.in/gTd5tTmb

Most docs teams are sitting on data that leadership actually wants — they just haven't framed it that way. Only 11–12% of docs teams track business outcomes like revenue or conversions. But the signal is already there: in your search logs, your support tickets, your product analytics. In our latest post, we walk through five practical ways to connect documentation work to metrics that matter to engineering, product, support, and leadership — things like: → The cost of doc-gap support tickets → Features shipped without docs (and the ticket spike that follows) → Time-to-first-success for users who engage with your docs vs. those who don't Read more on what you should be tracking: https://lnkd.in/e_dCS46J