Pinned
The State of Docs Report 2026 is live — insights from documentation experts across the industry on AI's growing role, how teams are measuring success, and where there are still gaps.
Read the full report here: buff.ly/yMjIIsX
GitBook
1,451 posts
GitBook
@GitBookIO
The docs platform for technical teams and AI agents
- GitBook Agent keeps on getting better. Most AI writing tools start from scratch. Agent starts with everything — your team's docs, your writing style, your connected sources, and even works in GitHub, Linear, and Slack.
See how GitBook Agent can work for your team: - Making your docs AI-ready isn't enough. If your content is outdated, llms.txt and MCP support just means AI agents confidently give users the wrong answer. Our Head of Engineering wrote on why quality still matters most.
- Using @SlackHQ, @github, or @linear? We’re running a webinar today on keeping your GitBook docs up to date from your favorite tools without leaving any context behind. Join us here: gitbook.com/events/channels
- Using update blocks with tags? Visitors on your published site can filter by tag to find exactly what they're looking for — new releases, fixes, improvements, you name it Learn more (and try it yourself!) in our changelog:
- Want to evolve your documentation skills for 2026? Sarah’s latest post offers a ton of practical advice. Here are the headlines: 🔄 Think in systems, not pages – consistency and relationships are everything 🤔 Get better at judgement than drafting – make the most of your
- The #1 docs challenge for product teams is keeping them up to date. GitBook Channels fixes that — trigger a change request by mentioning @GitBookIO in a thread, without leaving your tools. Join us on June 23rd 👉 gitbook.com/events/channels
- AI changes who reads your docs. It doesn't change who they're for. GitBook Docs Lead Sarah 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:
- We brought GitBook Agent directly into the editor. Open it from a new floating panel, handle updates inline, and add it as a reviewer on all of your changes. Free plan users can now try it too, with a weekly limit that resets automatically. Read more: gitbook.com/docs/changelog
00:00 - "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
- 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: buff.ly/yXPMVZR
- @GammaApp 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: gitbook.com/switch
See their docs in action: - 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
