We’re building the future of documentation

We’ve talked about a lot of new features over the past few weeks. Upgraded insights that let you measure more useful docs usage data. Computed content that can generate auto-updating docs in seconds. Adaptive content that gives every user a personalized experience — beyond simple, pre-filled API keys.

These are all powerful by themselves, but we’re not thinking about or building them as standalone features. Instead, this is a suite of tools that power the next generation of documentation.

We’ve said this a lot recently, but it bears repeating: we’re focused on building the future of documentation. That’s why we established the State of Docs Report 2025 — to share a clearer understanding of the documentation landscape today, and to make sure we’re on the right track for what’s coming next using insights from experts like you.

So here’s what we see as the future of docs — and how we’re helping to shape it.

Modern docs can’t just be static websites

Dynamic, adaptive documentation — integrated into the places your users are — is where we see the future of docs.

First, it needs to be easier for you and your team to update and maintain docs. And that means simplifying the process with useful tools and integrations.

But great docs shouldn’t only be easy to build and maintain for your team. They need to adapt to individual users to offer an advanced, personalized experience. And they need to give people the information they need when and where they need it — whether that’s in a support chat, or within your product itself.

But beyond that, it’s also vital that documentation creators like you can understand the true value of the docs you’re building. Measuring success is one of the biggest challenges documentation teams face, so it’s important that you can access detailed metrics about how users are interacting with your docs, and whether they’re meeting their goals.

Computed content creates and updates docs automatically

We all know that keeping documentation up-to-date is a huge challenge for docs teams everywhere. But when the information you need to update your docs already exists in other locations, software should break down the barriers that stop updates happening automatically.

With computed content, we’re taking our first steps to build this software solution. Computed content pulls information from pre-existing content, and uses it to create documentation in seconds, with limited manual effort.

Right now, that means you can create API documentation in GitBook from an OpenAPI spec in literally five clicks. And soon, it will mean you can localize your existing docs into any language you want in seconds using built-in AI.

Best of all, because this computed content uses an existing source to create your docs, it can also update automatically when that source changes.

So when you edit your OpenAPI spec, your docs update automatically. And when you edit your source docs, the AI translates those edits and updates your localized variants on your published site instantly.

Personalization that goes beyond simple API keys

When it comes to personalization, you shouldn’t have to settle for simply pre-filling API keys for your users. The future of docs personalization goes far beyond that.

Imagine unique landing pages for each of your pricing plans — so your users instantly see information about the features they have access to. Or site sections that will show or hide depending on whether someone has access to a specific feature flag in your product. Your docs could even suggest topical content related to a task your customers were just in the process of completing within your product.

Earlier this week, Steven talked about adaptive content — a solution that takes the idea of personalized docs to completely new levels.

In other words, we’re making this a reality in GitBook.

Adaptive content will offer advanced personalization built right into the GitBook platform. So you can build a single docs site with all the variations of content for different user groups — then show individual users only the content that’s relevant to them.

We’re also looking into ways to integrate this personalized content more deeply into product experiences. So your users can view or access adaptive content without having to navigate to your docs site.

Insights to track success and conversion

How do you and your team measure success in your docs? Page views? Written user feedback? Or perhaps you’re one of the 39% of docs professionals that don’t track any metrics at all?

However you’re doing it, we can all agree that the methods available today are too limited — or too time-consuming — to be useful. And we want to solve that.

Imagine analytics that could track specific conversion paths. You could use this to understand how docs usage relates to key business outcomes like signups, feature adoption, or support ticket reduction.

Our new insights set the foundations for this. First, we plan to let you filter analytics based on customer segments. So you’ll be able to see the different docs usage between enterprise customers and other customers, or how experienced users browse docs compared to your brand new customers.

These metrics won’t just make it easier to prove the value of your docs to stakeholders. They’ll also help you narrow down user pain points, knowledge gaps, and other improvements you can make across your docs sites.

And one more thing, coming soon

When it comes to finding those knowledge gaps or areas for improvement, we have another feature in the works that we’re not quite ready to talk about yet.

Without giving too much away, the idea is that GitBook will use AI to proactively identity customer pain points and the AI can then make suggestions for documentation edits that help address them.

We’ll have more to share in a few weeks, but it’s another tool we think will help you maintain and improve your docs, while saving you time on customer research or data analysis.

Together, this represents the future of docs

Right now, all of these features are still in their infancy. But these are huge first steps in our mission to build the next generation of documentation.

The first computed content feature — OpenAPI docs generation — is available right now. And adaptive content, auto-translation, and insights improvements are all coming very soon. We’re talking weeks, not months.

In the next few weeks, we’ll talk about all these features in more detail. And going forward, we’ll continue to expand and add new functionality to make your docs an even better resource for your users.

Stay tuned for more. And don’t forget to join our GitHub community to see the latest news and announcements, or to talk to us about features you’d like to see.

→ Get started with GitBook for free

→ Give every user their own docs experience with adaptive content

→ Computed content: What is it and how is it helping us shape the future of docs?

We’ve talked about a lot of new features over the past few weeks. Upgraded insights that let you measure more useful docs usage data. Computed content that can generate auto-updating docs in seconds. Adaptive content that gives every user a personalized experience — beyond simple, pre-filled API keys.

These are all powerful by themselves, but we’re not thinking about or building them as standalone features. Instead, this is a suite of tools that power the next generation of documentation.

We’ve said this a lot recently, but it bears repeating: we’re focused on building the future of documentation. That’s why we established the State of Docs Report 2025 — to share a clearer understanding of the documentation landscape today, and to make sure we’re on the right track for what’s coming next using insights from experts like you.

So here’s what we see as the future of docs — and how we’re helping to shape it.

Modern docs can’t just be static websites

Dynamic, adaptive documentation — integrated into the places your users are — is where we see the future of docs.

First, it needs to be easier for you and your team to update and maintain docs. And that means simplifying the process with useful tools and integrations.

But great docs shouldn’t only be easy to build and maintain for your team. They need to adapt to individual users to offer an advanced, personalized experience. And they need to give people the information they need when and where they need it — whether that’s in a support chat, or within your product itself.

But beyond that, it’s also vital that documentation creators like you can understand the true value of the docs you’re building. Measuring success is one of the biggest challenges documentation teams face, so it’s important that you can access detailed metrics about how users are interacting with your docs, and whether they’re meeting their goals.

Computed content creates and updates docs automatically

We all know that keeping documentation up-to-date is a huge challenge for docs teams everywhere. But when the information you need to update your docs already exists in other locations, software should break down the barriers that stop updates happening automatically.

With computed content, we’re taking our first steps to build this software solution. Computed content pulls information from pre-existing content, and uses it to create documentation in seconds, with limited manual effort.

Right now, that means you can create API documentation in GitBook from an OpenAPI spec in literally five clicks. And soon, it will mean you can localize your existing docs into any language you want in seconds using built-in AI.

Best of all, because this computed content uses an existing source to create your docs, it can also update automatically when that source changes.

So when you edit your OpenAPI spec, your docs update automatically. And when you edit your source docs, the AI translates those edits and updates your localized variants on your published site instantly.

Personalization that goes beyond simple API keys

When it comes to personalization, you shouldn’t have to settle for simply pre-filling API keys for your users. The future of docs personalization goes far beyond that.

Imagine unique landing pages for each of your pricing plans — so your users instantly see information about the features they have access to. Or site sections that will show or hide depending on whether someone has access to a specific feature flag in your product. Your docs could even suggest topical content related to a task your customers were just in the process of completing within your product.

Earlier this week, Steven talked about adaptive content — a solution that takes the idea of personalized docs to completely new levels.

In other words, we’re making this a reality in GitBook.

Adaptive content will offer advanced personalization built right into the GitBook platform. So you can build a single docs site with all the variations of content for different user groups — then show individual users only the content that’s relevant to them.

We’re also looking into ways to integrate this personalized content more deeply into product experiences. So your users can view or access adaptive content without having to navigate to your docs site.

Insights to track success and conversion

How do you and your team measure success in your docs? Page views? Written user feedback? Or perhaps you’re one of the 39% of docs professionals that don’t track any metrics at all?

However you’re doing it, we can all agree that the methods available today are too limited — or too time-consuming — to be useful. And we want to solve that.

Imagine analytics that could track specific conversion paths. You could use this to understand how docs usage relates to key business outcomes like signups, feature adoption, or support ticket reduction.

Our new insights set the foundations for this. First, we plan to let you filter analytics based on customer segments. So you’ll be able to see the different docs usage between enterprise customers and other customers, or how experienced users browse docs compared to your brand new customers.

These metrics won’t just make it easier to prove the value of your docs to stakeholders. They’ll also help you narrow down user pain points, knowledge gaps, and other improvements you can make across your docs sites.

And one more thing, coming soon

When it comes to finding those knowledge gaps or areas for improvement, we have another feature in the works that we’re not quite ready to talk about yet.

Without giving too much away, the idea is that GitBook will use AI to proactively identity customer pain points and the AI can then make suggestions for documentation edits that help address them.

We’ll have more to share in a few weeks, but it’s another tool we think will help you maintain and improve your docs, while saving you time on customer research or data analysis.

Together, this represents the future of docs

Right now, all of these features are still in their infancy. But these are huge first steps in our mission to build the next generation of documentation.

The first computed content feature — OpenAPI docs generation — is available right now. And adaptive content, auto-translation, and insights improvements are all coming very soon. We’re talking weeks, not months.

In the next few weeks, we’ll talk about all these features in more detail. And going forward, we’ll continue to expand and add new functionality to make your docs an even better resource for your users.

Stay tuned for more. And don’t forget to join our GitHub community to see the latest news and announcements, or to talk to us about features you’d like to see.

→ Get started with GitBook for free

→ Give every user their own docs experience with adaptive content

→ Computed content: What is it and how is it helping us shape the future of docs?

We’ve talked about a lot of new features over the past few weeks. Upgraded insights that let you measure more useful docs usage data. Computed content that can generate auto-updating docs in seconds. Adaptive content that gives every user a personalized experience — beyond simple, pre-filled API keys.

These are all powerful by themselves, but we’re not thinking about or building them as standalone features. Instead, this is a suite of tools that power the next generation of documentation.

We’ve said this a lot recently, but it bears repeating: we’re focused on building the future of documentation. That’s why we established the State of Docs Report 2025 — to share a clearer understanding of the documentation landscape today, and to make sure we’re on the right track for what’s coming next using insights from experts like you.

So here’s what we see as the future of docs — and how we’re helping to shape it.

Modern docs can’t just be static websites

Dynamic, adaptive documentation — integrated into the places your users are — is where we see the future of docs.

First, it needs to be easier for you and your team to update and maintain docs. And that means simplifying the process with useful tools and integrations.

But great docs shouldn’t only be easy to build and maintain for your team. They need to adapt to individual users to offer an advanced, personalized experience. And they need to give people the information they need when and where they need it — whether that’s in a support chat, or within your product itself.

But beyond that, it’s also vital that documentation creators like you can understand the true value of the docs you’re building. Measuring success is one of the biggest challenges documentation teams face, so it’s important that you can access detailed metrics about how users are interacting with your docs, and whether they’re meeting their goals.

Computed content creates and updates docs automatically

We all know that keeping documentation up-to-date is a huge challenge for docs teams everywhere. But when the information you need to update your docs already exists in other locations, software should break down the barriers that stop updates happening automatically.

With computed content, we’re taking our first steps to build this software solution. Computed content pulls information from pre-existing content, and uses it to create documentation in seconds, with limited manual effort.

Right now, that means you can create API documentation in GitBook from an OpenAPI spec in literally five clicks. And soon, it will mean you can localize your existing docs into any language you want in seconds using built-in AI.

Best of all, because this computed content uses an existing source to create your docs, it can also update automatically when that source changes.

So when you edit your OpenAPI spec, your docs update automatically. And when you edit your source docs, the AI translates those edits and updates your localized variants on your published site instantly.

Personalization that goes beyond simple API keys

When it comes to personalization, you shouldn’t have to settle for simply pre-filling API keys for your users. The future of docs personalization goes far beyond that.

Imagine unique landing pages for each of your pricing plans — so your users instantly see information about the features they have access to. Or site sections that will show or hide depending on whether someone has access to a specific feature flag in your product. Your docs could even suggest topical content related to a task your customers were just in the process of completing within your product.

Earlier this week, Steven talked about adaptive content — a solution that takes the idea of personalized docs to completely new levels.

In other words, we’re making this a reality in GitBook.

Adaptive content will offer advanced personalization built right into the GitBook platform. So you can build a single docs site with all the variations of content for different user groups — then show individual users only the content that’s relevant to them.

We’re also looking into ways to integrate this personalized content more deeply into product experiences. So your users can view or access adaptive content without having to navigate to your docs site.

Insights to track success and conversion

How do you and your team measure success in your docs? Page views? Written user feedback? Or perhaps you’re one of the 39% of docs professionals that don’t track any metrics at all?

However you’re doing it, we can all agree that the methods available today are too limited — or too time-consuming — to be useful. And we want to solve that.

Imagine analytics that could track specific conversion paths. You could use this to understand how docs usage relates to key business outcomes like signups, feature adoption, or support ticket reduction.

Our new insights set the foundations for this. First, we plan to let you filter analytics based on customer segments. So you’ll be able to see the different docs usage between enterprise customers and other customers, or how experienced users browse docs compared to your brand new customers.

These metrics won’t just make it easier to prove the value of your docs to stakeholders. They’ll also help you narrow down user pain points, knowledge gaps, and other improvements you can make across your docs sites.

And one more thing, coming soon

When it comes to finding those knowledge gaps or areas for improvement, we have another feature in the works that we’re not quite ready to talk about yet.

Without giving too much away, the idea is that GitBook will use AI to proactively identity customer pain points and the AI can then make suggestions for documentation edits that help address them.

We’ll have more to share in a few weeks, but it’s another tool we think will help you maintain and improve your docs, while saving you time on customer research or data analysis.

Together, this represents the future of docs

Right now, all of these features are still in their infancy. But these are huge first steps in our mission to build the next generation of documentation.

The first computed content feature — OpenAPI docs generation — is available right now. And adaptive content, auto-translation, and insights improvements are all coming very soon. We’re talking weeks, not months.

In the next few weeks, we’ll talk about all these features in more detail. And going forward, we’ll continue to expand and add new functionality to make your docs an even better resource for your users.

Stay tuned for more. And don’t forget to join our GitHub community to see the latest news and announcements, or to talk to us about features you’d like to see.

→ Get started with GitBook for free

→ Give every user their own docs experience with adaptive content

→ Computed content: What is it and how is it helping us shape the future of docs?