GitBook

““I basically just said, ‘Okay everyone, we’re using GitBook, here you go.’ And everyone was able to jump in and start making edits instantly. I think that’s quite telling — if engineers can just pick up a thing and start using it, then that’s a big deal.””

““I think so much of the stuff I care about is the presentation layer. How do I set the Favicon for my site, for example? I think GitBook has the right ethos — ‘let’s make sure that this stuff looks beautiful‘.””

““We run all that using Trunk on our own GitBook. It’s really an awesome way to keep the documentation efficient but in a way that’s still nicely presented.””

““I love the ability to go in and edit locally through the WYSIWYG editor. But then when there are large changes, I can go in and bulk edit with my IDE, and do a global search and replace. That’s super powerful.””

““Our marketing site is for product-focused people. But most engineers will look right past all that and head to the docs for the nuts and bolts. So we invest heavily into making sure our docs are detailed, inviting and modern.””

““Giving them the ability to use a tool and system they’re comfortable with is super helpful and saves everyone time,””

““It’s a great way to get people across the team to proofread and see things as they would appear in production. It’s nice for them to have frictionless access to content without needing to log in or navigate the tool.””

““GitBook is our main form of documentation for our customers and their development teams. Initially, it was strictly for our API reference, but over time it’s expanded to include tutorials, how-to guides, and even some end-user documentation.””

“Editing feels just like working in a Google Doc. Your whole team can work simultaneously, even on the same page.”

“GitBook has boosted our SEO, making Unsloth more visible in search results and ChatGPT pulls.”

“GitBook has helped us dramatically, so much that it’s essentially replaced our main website.”

“There’s always a new feature or refinement [in GitBook]. The design keeps evolving, and everything looks so modern and thoughtful.”

““It's that flexibility and trust in the process that allows us to keep our knowledge base accurate and responsive, even as a small team, where time is scarce, and the product is constantly evolving.””

““We can create a new article in one section while simultaneously updating another topic in a different section. Each edit is reviewed independently, so we're never blocked waiting on a single review or worried about overwriting changes or losing base content.””

““For modern software organizations, it’s good to stick together, and we found a really good partner in GitBook.””

““We are able to use our documentation for prospects, not just for customers. Finding a certain page in Google is just way easier with GitBook. Now I can actually see traffic from outside the app, which previously was not the case.””

““We organized a session in the product team where we distributed pages to everyone, where everyone would take something like 15 pages. And we were able to move everything in three or four hours.””

““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.””

““We want everyone to be able to contribute to documentation, so it’s not just the product team that owns it. We want every single engineer to be able to go and contribute and edit an article or add a new article on the topic they’re exploring. So we want to have the threshold as low as possible for contributing.””