We’ve been testing this feature internally, and it’s been night and day on making improvements to our docs.
Excited to launch this today!
P.S. have you seen our new docs?
gitbook.com/docs/
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.
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/
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/
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.
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…
AI visitors now outnumber human ones on doc sites — and most teams have no idea what they're actually asking.
AI insights shows you the exact questions users ask, where your docs fall short, and what to fix.
I'm hosting a webinar Tuesday to dive in: bit.ly/4mbjErI
AI visitors now outnumber humans on doc sites. Your docs aren't just for developers anymore — they're the context AI draws from to represent your product. We built something to close that loop.
Read more about what we’re launching: buff.ly/L7nqtyd
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
Something I wanted in @GitBookIO for a while: you can now embed an Ask AI input directly in your docs pages — right where users land.
Already dogfooding it in our own guides → gitbook.com/docs/guides
AI now accounts for 41% of docs readers — up from 9% at the start of 2025.
That’s a 500% increase in AI readership in one year.
Docs aren’t just read by humans anymore. They’re read for humans, by AI.
Read more about what this shift means for docs: buff.ly/bZEhG8O
We’re collecting surveys for our next iteration of the State of Docs report!
Last year, we uncovered some pretty amazing trends, especially around how teams are thinking about AI in their docs.
This year, we’re going deeper.
Add your voice: stateofdocs.com/
The State of Docs survey is back. 📚
Last year, hundreds of people shared their voices and helped us prove docs matter. This year, we’re going deeper on AI, scale, and how docs get shipped and maintained.
If you write, read, or depend on docs, take 5 minutes and add your voice:
stateofdocs.com/2026/survey
4 years ago I started building brillapp.com as a side project to help myself learn languages better.
Today, I launched it again with more features — cleaner, faster, and way more intentional about how you’re able to memorize vocabulary
Just released version (2.0) with 25 languages - giving away 3 pro subscriptions to the first to download and dm me your email
Happy new year!
apps.apple.com/us/app/brill-…
We’re wrapping up 2025 at GitBook with a lot of pride. This year wasn’t just about shipping features—it was about redefining what documentation should be for modern technical teams.
I’ve also added support for 15 languages — Japanese, Korean, Cantonese, Mandarin, Hokkien, Filipino, French, German, Italian, Malay, Portuguese, Spanish, Swedish, Danish, and Dutch
🇯🇵🇰🇷🇭🇰🇨🇳🇹🇼🇵🇭🇫🇷🇩🇪🇮🇹🇲🇾🇵🇹🇪🇸🇸🇪🇩🇰🇳🇱