Explore how adaptive content transforms your docs into a dynamic, tailored experience for every user.
Read the docs
PricingLog inSign up

1 August: GitBook Assistant, improved insights, new AI actions and more

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

✨ New and noteworthy

GitBook Assistant — knowledge from your docs and beyond

As part of yesterday’s adaptive content launch we also introduced GitBook Assistant — 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 connect to other sources via MCP servers, 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.

Time ranges and AI response rating in insights

We’ve made two big improvements to our built-in insights.

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.

Page actions

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.

Semantic colors in the editor

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.

New “Wide” page width option

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.

Page metadata

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.

OpenAPI spec validation improvements

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.

Improved

  • You can now add comments on individual table cells, allowing for better feedback when collaborating on complex pages.

  • We’ve added some new shortcuts to table blocks. You can now hit ⌘ + / (Or Ctrl + / on PC) to open the Row options menu, and hit ⌘ + - (or Ctrl + - on PC) to delete the row containing the currently-selected block.

  • We’ve made locked live edits the default editing mode in new spaces, which means the default workflow in GitBook will now be using change requests. This is already the case for all published content, and brings us closer to the Git workflow. For now, you can toggle live edits on a space to re-enable live editing if needed.

  • We’ve reduced the padding in inline code to make it feel a little more compact and in line with the rest of your content.

  • We now show icons in the table of contents that denote when a page is hidden and/or not indexed in search. If a page is both hidden and not indexed, we show both icons together to avoid taking up too much space in the TOC.

  • The spacing in the table of contents now makes it clearer when spaces are part of groups or separate from them. Before, spaces directly below page groups would be so close to the group that they appeared to be part of the group.

Fixed

  • Fixed a bug that meant holding ⌘ or Cmd and clicking in the sidebar was causing the app to freeze.

  • We’ve removed TypoScript from the code syntax dropdown menu as it was confusingly similar to TypeScript and far less popular.

  • Fixed a bug that meant drawings weren’t updating immediately in the editor when you made changes to the drawing itself.

  • Disabled the shortcut to activate search within the GitBook app, as it was causing conflicts with other system shortcuts for some users.

  • Fixed a bug that meant hitting Esc while in the emoji selector didn’t just close the menu, but also selected the current block.

  • Fixed an issue that meant your AI writing prompt would be lost if AI was used at the bottom of a page — and another that meant very long AI writing prompts could grow past the total height of the page.

  • Fixed a bug that meant empty pages would sometimes display at full-width even if you didn’t select it.

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.

Last updated

Was this helpful?