This release introduces a supercharged new AI assistant, improved insights options, a new wider page width option that’s perfect for building landing pages, and much more
Last updated
Was this helpful?
Was this helpful?
As part of yesterday’s we also introduced — a powerful new AI experience for your docs.
Assistant is a big step up over our previous AI search functionality. While our old solution was fast and gave end-users accurate answers based on your docs, GitBook Assistant offers a new chat-based UI, seamless integration with adaptive content, and the option to connect with MCP servers to provide better answers with more context.
As well as using agentic retrieval — which gives it a deeper understanding of user intent, and more accurate responses — it’s also integrated with adaptive content. So it can use knowledge about an individual user to give better, more tailored answers.
It can also , meaning GitBook Assistant can pull information from different sources and use that information to answer questions with even more context.
Read more in our announcement post, or head to our demo site to experience its adaptive content integration.
We’ve made two big improvements to our built-in .
First, you can now choose time ranges when analyzing site data. So you can set custom time periods to review, or compare site data between two identical periods in any degree of separation.
Plus, you’ll now also see the ratings that users are giving your AI responses within the Insights panel — along with the question they asked and how many people asked similar things.
This is ideal for identifying common questions that are getting poorly-rated answers, so you can fill the gaps in your docs and provide better answers to your users.
Your docs now feature a handy Page actions menu on each page, allowing your users to quickly ask GitBook Assistant a question, view or copy the page content in Markdown, or open the page in ChatGPT or Claude to pre-load a prompt.
You can now use the semantic colors you define for your docs site — which are used to change the color of hint blocks and announcement banners in your docs — within the content itself.
If you’ve set semantic colors for a docs site and are editing the content of that site in a change request, you can now use the inline palette to change the text color and background to use the Primary, Info, Success, Warning or Danger colors you’ve defined for that site. These colors will sync with the semantic colors in your docs to bring everything in line.
We’ve added a new Wide page width option, which is perfect for creating eye-catching landing pages.
To enable the option, open the page you want to widen and open the Page options menu that appears when you hover over the page title.
There, you can set the page width to Wide, which will automatically expand all blocks that can be expanded, and align the rest of the blocks within the bigger container.
Head over to our demo site to see how it looks.
GitBook automatically creates page metadata — including when the page was updated and who updated it. These are both shown by default in the editor, and ‘Last updated’ also appears on published pages.
Now, you have the option to disable that metadata on a per-page basis. Open the Page options menu and in the Footer section disable the Page metadata option to hide the data from readers.
We’ve made some improvements to our OpenAPI specification validation process. These updates should identify issues with the spec file earlier, so your docs stay consistent and reliable for your readers.
If you’ve experienced any issues with your OpenAPI spec in GitBook, try pasting it into http://editor.swagger.io/ to check for formatting or structural problems. And if you’re still having trouble validating your spec, feel free to reach out to our support team at support@gitbook.com.
We’re constantly working to improve the way you and your team work in GitBook, and value your input on features, bugs, and more. Make sure you head to our official GitBook community to join the discussion.
