GitBook

One thing I've wanted for a while in our own docs: drop an Ask AI input right in the middle of a page — dead center for people to get started with GitBook faster. Just shipped, and now dogfooding it in our own docs! You can now add inline buttons that trigger GitBook Assistant, search, or a preset query. Check it out: https://lnkd.in/eWS5W-9w

We’re excited to announce that we've migrated our documentation platform to GitBook! We're always looking to reduce friction for our users, and that includes having the right information when you need it. By moving to GitBook, we're able to provide an improved docs experience. What’s improved? 🔹𝐌𝐨𝐝𝐞𝐫𝐧 𝐝𝐞𝐬𝐢𝐠𝐧: improved accessibility, readability and layout; 🔹𝐈𝐦𝐩𝐫𝐨𝐯𝐞𝐝 𝐧𝐚𝐯𝐢𝐠𝐚𝐭𝐢𝐨𝐧: a cleaner, more organized structure; 🔹𝐁𝐞𝐭𝐭𝐞𝐫 𝐬𝐞𝐚𝐫𝐜𝐡 𝐚𝐧𝐝 𝐀𝐈 𝐚𝐬𝐬𝐢𝐬𝐭𝐚𝐧𝐭: easier to find what you're looking for; 🔹𝐌𝐂𝐏 𝐬𝐞𝐫𝐯𝐞𝐫: connect balena docs to your preferred LLMs and external tooling; 🔹𝐓𝐡𝐞𝐦𝐞 𝐜𝐮𝐬𝐭𝐨𝐦𝐢𝐳𝐚𝐭𝐢𝐨𝐧: toggle between light, dark, or match system modes (bottom right corner); 🔹𝐀𝐏𝐈 𝐩𝐥𝐚𝐲𝐠𝐫𝐨𝐮𝐧𝐝 (𝐛𝐞𝐭𝐚): test endpoints directly in your web browser. Read more about the move, the enhancements, and see the new look for yourself: 📖 𝐁𝐥𝐨𝐠: https://lnkd.in/ePuK92Fd 🔗 𝐃𝐨𝐜𝐬: https://docs.balena.io/ Let us know what you think! #balena #GitBook #IoT #DevDocs #Documentation #ProductUpdate

AI agents, IDEs, and LLMs are constantly viewing your docs. Cursor is searching your API reference, Claude is pulling your setup guide, Codex is fetching your SDK docs, but none of it is showing up in your analytics. We just shipped two things at GitBook: - MCP Analytics: A dedicated dashboard for traffic coming through your docs' public MCP. See exactly what queries AI tools are making against your docs, and how often. - Improved Agent Tracking: Cursor, Claude Code, and other AI tools now appear as distinct visitor types. If your top MCP query has no dedicated page, that's a gap worth fixing 👀

You could think building an app ends when it ships on the App Store… But that’s really just the beginning. Once your app is released, people start using it. From that point on, you must do everything in your power to make every feature clear and easy to use, improve processes that felt logical to you, but not to your customers, and help them understand how to achieve what they wanted to achieve when they downloaded the app. Yeah. That’s a lot of work. At The Grizzly Labs, we’re a team of 10 building apps used by millions. Most of our users are on the free tier… and yet our bar for support quality is extremely high. We aim to answer most people within 24 hours. For a team our size, that’s ambitious. That goal is impossible without: - solid internal processes, - tight collaboration across dev, support, sales, and product, - and documentation that actually helps users help themselves. It came a point we had reached the limits of our previous knowledge base… It worked, yes, but it was becoming harder to maintain, harder to evolve, harder to collaborate on. We felt we were wasting more and more time trying to keep it running, and the quality of our help articles was impacted. So we decided it was time to look for another solution more suited to our needs. Migrating an entire knowledge base is not glamorous… but it’s a rare opportunity to clean things up, rethink the structure, remove outdated content, and improve clarity. To do so, we needed: - git-based workflows to make reviews and validation easy across teams, - real multi-user collaboration without friction, - strong discoverability (search, AI assistance, SEO) to maximize self-resolution, - a tool that’s efficient and pleasant to use, because when you’re few, you can’t waste time with difficult setups and confusing processes. We eventually settled on GitBook. For some, it might feel like an odd choice. Indeed, it’s often associated with developer documentation, but we liked the clean structure and collaborative workflow. It felt like a solid foundation for a consumer app knowledge base. How the migration went On the technical side, importing everything was just smooth. From a content perspective, the modular approach made things easy. Reusable blocks, a clean structure, and a well-organized image library (naming matters!) helped a ton. Compared to tools where formatting breaks easily or requires too much code, this felt refreshingly straightforward.  Also, it gave us a great opportunity to rethink our structure, clean up outdated articles, add missing ones, and improve clarity overall. Compared to our previous setup  GitBook feels: - more modern - easier for collaborative reviews - better in terms of reporting and visibility Overall, the move helped us improve both how we write documentation and how users experience it. If you’re maintaining a growing help center with multiple contributors, it’s definitely worth a look. ➡️ https://lnkd.in/ebGyGqax