GitBook 3.0: Document everything, from start to ship
Learn more about what we're launching today, alongside our vision for a Git-powered future.
We've been lucky to rely heavily on product-led growth and with that comes the countless hours we've spent talking to customers. We’ve heard the frustration firsthand from technical teams who say some of their biggest engineering challenges are around finding and writing documentation. Most companies are relegated to using all-in-one editing tools like Google Docs or Dropbox Paper, which aren’t built for sharing or hosting technical knowledge. Others invest thousands of hours and resources building internal developer portals, which are often poorly maintained and accessed.
The result is a documentation process that is disconnected from the developer workflow, making technical documentation an afterthought. Not to mention, a costly burden on developer productivity. Here’s where GitBook is a no-brainer, as an out-of-the-box docs-as-code platform that allows technical teams to use a Git workflow to create, collaborate on and share documentation.
GitBook's customers today are able to net huge development wins by consolidating all technical documentation on a central platform, using a change request workflow to continuously collaborate on and better documentation. GitHub and GitLab integrations also means developers can commit directly from repositories, making it easy to maintain and update docs.
GitBook has long been a standard for public docs, which is why, in this launch, we've made concerted efforts to improve how user-facing documentation looks, with modern updates to the look and feel, alongside new ways to design landing pages. Increasingly we're also seeing teams use the same Git workflow for internal technical knowledge—from onboarding, RFCs and tutorials, to code structure/dependencies, and best coding practices.
In GitBook today, you'll find a whole host of new integrations designed to empower teams to get the job done more efficiently—from collaboration and security to bug tracking and more. Over the coming months, we'll open up our platform to allow any developer to build custom integrations for GitBook.
We envision a future in which GitBook becomes embedded left-of-code, where developers and larger product teams can collaborate on any type of internal or external documentation using the Git workflow. The work around integrations is just starting, but if you're interested, we're beginning to partner with select developers to build the first community-powered integrations for the platform. Apply here. For more details on what exactly shipped in GitBook 3.0, check out our changelog.