web stuff | developer relations @GitBookIO | prev @framer @miroHQ

Tokyo-to, Japan
Over the last few weeks, we rebuilt @GitBookIO's docs from scratch. We started by digging into the data on what new and existing users were actually trying to do when they landed in our docs. 🧵
1
2
272
Over the last few weeks, we rebuilt @GitBookIO's docs from scratch. We started by digging into the data on what new and existing users were actually trying to do when they landed in our docs. 🧵
1
2
272
Since launch, support gets fewer "where do I find…" questions, and our AI insights show a clear shift in what people are asking about getting started. Very happy with how it turned out!
1
28
Super excited for the swag we’ve been cooking up for @GitBookIO this year 👀 Come meet me and the team at one of our upcoming events and we’ll give you some! Register at gitbook.com/events
1
1
167
More and more @GitBookIO teams are using our MCP to create and manage their docs — and it's exciting to hear how flexible it’s been for different use-cases. If you haven't tried the GitBook MCP yet, I wrote a quick guide with some best practices: gitbook.com/blog/create-docu…
1
3
359
Proud to have contributed to this one! The State of AI Search for Dev Tools 2026 confirms what we're seeing at @GitBookIO : docs are becoming AI infrastructure. AI reads them before it recommends a tool for you. Read the full report: devtune.ai/dev-tools-state-o…
Replying to @theplgeek
This report is much richer because of the practitioners that contributed their own observations from the field. Thanks to the following folks for sharing your experience so generously. @addisonschultz - @GitBookIO @_Dapp - @clerk @BarrieSegal - Kind Stranger Chris Bright - @depotdev Dan Poppy - @dbt_labs @gandharva - @measure_sh Holly White - @GearsetHQ continued...
1
202
AI agents are only as good as the context you give them — that's why skill.md files are taking off right now Auto-generating one from your docs is fast but inherits every gap. Writing by hand is precise but slow.
1
533
These numbers are crazy when you actually think about it 👀
Agent traffic is still on the rise — and it just crossed a new threshold. AI agents now account for 51.8% of intentional reads across GitBook-hosted docs. Up from less than 10% in January 2025. For the first time, they outnumber humans.
1
159
Added a few more locations 🗼
I've been falling down a rabbit hole of Tokyo neighborhood names — 三軒茶屋 means "three teahouses," 目黒 means "black eye." I quickly made an app to explore Tokyo neighborhoods and their kanji to understand their meaning. Explore for yourself: chimei.vercel.app/
1
122
We’re experimenting with better instructions for agents in your @GitBookIO docs 🤖 Now live on all sites with GitBook Assistant enabled!
1
4
154
I've been falling down a rabbit hole of Tokyo neighborhood names — 三軒茶屋 means "three teahouses," 目黒 means "black eye." I quickly made an app to explore Tokyo neighborhoods and their kanji to understand their meaning. Explore for yourself: chimei.vercel.app/
2
342
I’m seeing the same story over and over when it comes to docs: Most teams don't know what their docs are actually doing. We just shipped AI insights at @GitBookIO: a bird's-eye view of how your users are getting answers from GitBook Assistant.
2
1
120
This is part of a bigger picture: docs that don't just sit there, but actively surface what needs to improve. We're shipping more soon on closing that loop, making it easier to act on what you learn. Check it out in our launch from last week: gitbook.com/blog/close-the-p…
1
58