GitBook

““When you’re working on a new feature, you ensure that the documentation of that feature is up to date. So it’s the engineer implementing the feature that then goes and checks the documentation. This way you just get everyone exposed to how we write about our features and they get a chance to contribute.””

““Everyone is using the editor, it’s just a way faster experience to do things. Engineers are using that as well just because it’s faster to do things in the UI, and you can ensure that it looks good for the customer.””

““What’s really important is being able to maintain all the content at scale. For example, what if we change a feature name tomorrow? When it lives in Markdown files, and it’s just a GitHub repository, it’s very easy to do.””

““We can integrate exactly the same content in the app. So we are just using the same Markdown files and just styling them and delivering them in the app. So it’s exactly the same content served in two places.””

““Pretty much everyone is familiar with GitHub and how you work with Git. So it was very easy to introduce GitBook from this perspective.””

““I feel it also gives us brand value, because you get the same quality experience that you would get with Swarmia. The GitBook style blends with our branding, and the customer doesn’t even need to know that it’s an extra tool.””

““The build quality is really the number one thing for us, because I really wanted the documentation to feel like an extension of a product and not just an extra thing. GitBook does that really well. The same quality standards that are applied to our product are definitely hit by GitBook.””

““GitBook is easy to use, and beautiful to look at. Its no-code styling and wide range of tools for displaying and organizing information make it easy for us to maintain our documentation as if it’s a product in its own right.””

““We’re able to get GitBook’s MCP hooked in for our partners so they can connect their agents to our documentation and produce their code via AI.””

““GitBook gave us the best of both worlds. It integrates seamlessly with our engineering stack, while offering our internal stakeholders an intuitive editing experience — no code editor required. Making updates is now fast and frictionless””

““I’m a great advocate of GitBook. The product is great. It's made our lives so much easier here at bunq, and we really enjoy using it.””

““We love how easy it is to work with the GitBook team. If there’s a feature that we want, they either build it, or show us how existing features can help. GitBook has always been a great partner to us.””

““I love the seamless integration with GitHub. It let me keep the existing pipelines, while simplifying the hard parts. I didn’t have to add any JavaScript or create HTML — just direct markdown.””

““Every day, I discover something new and think: wow, this is also there. AI insights, content gaps, broken links, style guides, and now AI agents in the editor itself.””

““On aesthetics, capability, usability, pricing, and AI features, GitBook was the clear winner. The team was collaborative and able to support all of our needs.””

““The GitBook design looks good out of the box, with many options to customize it further. A consistent experience across the product is key, and we enjoyed being able to make our docs on-brand.””

““Go for it! Using GitBook is a no-brainer — it’s beautifully crafted and developer-friendly. It makes your docs stand out. And so it does for your product, too.””

““We often release features that come with a docs page. We envision a future where docs are feature-flagged, just like the feature in the product.””

““As a developer-first company, we love that GitBook syncs with GitHub. We’ve integrated our developer docs hosted in GitHub with the rest of our docs easily.””

““We switched to GitBook as part of a design-driven decision. The GitBook design looks good out of the box — so we got a lot for ‘free’. More importantly, we had many options to customize the design of our docs. A consistent experience across the product is key, and we enjoyed being able to make our docs on-brand.””

““As a developer tool, documentation is one of the first things people seek out when evaluating Reflag. So it’s vital to us. Your experience should be consistent from the marketing site, to the docs, to the product. Both must reflect the care we put into polishing the details.””

““We believe our documentation is becoming a differentiator, and partners appreciate how straightforward our integration process is.””

““Partners now access our docs directly in Cursor, VS Code or Claude Code. That single change has noticeably reduced integration time and support requests.””

““We were answering the same integration questions in Slack and Telegram over and over. It wasn’t scalable.””

““All our docs are in GitHub, which means they’re accessible to our agents and part of our engineering process.””