GitBook

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

Open-ended questions are where most AI chat breaks down — answers get generic, inconsistent, or just too long. @zenoachtig wrote about how we tackled that with GitBook Assistant. Read more: buff.ly/BW8txf3

We’re hosting a webinar next week on working with GitBook’s skill file and Claude. Grab your spot here: buff.ly/48h0wYn

AI agents need more than API docs — they need context. Skill files gives them that. We wrote a guide on how to write one (and why your docs are the right place to host it). buff.ly/J4Rdsvc

Writing great documentation shouldn't require leaving your workflow. GitBook now lives inside @SlackHQ, @linear, and @github, so your team can keep docs up to date without losing a beat. Now live in GitBook: gitbook.com/docs/gitbook-a…

@vercel Read more on how we’re building GitBook: buff.ly/lBbnMDf

30k+ docs sites, 120M page views/month, 40k cache invalidations per day — each resolved in under 300ms. We spoke with @vercel and wrote on how we built the infra behind it: buff.ly/8e74Nkv

Join us on May 19th: gitbook.com/events/claude

If you're working in GitBook with Git Sync, using AI tools like Claude can help you work on your docs like an extra teammate would. GitBook ships with a skill.md file — a structured context file that tells AI tools how to write GitBook-flavored documentation. We're running a live demo to show exactly how it works: → What a skill.md file is and how to use it → How Git Sync and Claude use it together → A real walkthrough you can replicate in your own space

GitBook CEO @saratandowsky is taking the stage at @devworld_conf in Amsterdam today — talking through documentation, AI, and what it means for the future of product teams. Grab your tickets here: devworldconference.com

If you care where documentation is going next, this is for you. We’re hosting a State of Docs panel in San Francisco with leaders from @AnthropicAI, @salesforce, and more: – How AI is reshaping workflows – The shift from writing → reviewing – Where writers fit in an AI-first world Join us tonight: luma.com/e5r410lo

Almost half of all GitBook traffic comes from AI agents crawling docs. Read more on how we use @vercel to power our infrastructure 👇

We just made search in GitBook even better. Instant results, more relevant ranking, and a cleaner, more focused result view. Now live in all GitBook sites. Read more in our changelog: #faster-site-search-with-better-results" target="_blank" rel="nofollow noopener">gitbook.com/docs/changelog…

As Sandeep Medikonda from @ServiceNow puts it in the latest State of Docs report: “One of the most unique things humans possess is intuition.” That intuition, the context you build as a technical writer, is what makes docs valuable. The State of Docs report explores how that role is evolving. Read more: stateofdocs.com/2026/docs-and-…

@writethedocs Find the full schedule and secure your ticket here: buff.ly/aDOtYlF

The GitBook team is going to Portland! We’re excited to be sponsoring @writethedocs Portland next week. We’ll be giving demos, chatting all things State of Docs, and diving into what’s next for documentation.

Read more on how enterprises are structuring their docs for AI: buff.ly/fbtwZl5

46% of enterprise users now reach your docs through AI. How do your docs stack up against the shift?

Read more in our changelog: #gitbook-assistants-answers-are-now-more-elaborative-and-creative" target="_blank" rel="nofollow noopener">gitbook.com/docs/changelog…

Your docs should answer questions, not just contain information. GitBook Assistant just got smarter — more detailed, more creative, with recommended questions now in your site's language. And with AI insights, your docs show you exactly what users are asking, so you know what to fix.

The State of Docs report digs into where docs ownership is heading: stateofdocs.com/2026/docs-team…

Tech writing job descriptions are changing in 2026. "Part vibe coder, part data expert, part product manager, part business ops maven." Sound familiar?