2025

You now have powerful new options for inline buttons that include search and GitBook Assistant inputs — allowing your users to type a question and activate a search or Assistant chat right from the page.

Plus, you can also create disabled buttons or buttons that trigger a specific preset search or query of your choice.

Here are a few examples of things you can do with the new button actions…

Add a search button with a pre-set search parameter:

Create an empty search bar that users can type directly into to find a topic:

Embed a place for users to ask GitBook Assistant something about your docs:

Add a disabled button to show something is inactive:

You can configure all of these options by hitting / and choosing Button to add a button to your page, then clicking the button to open the Label menu.

You can now set the page metadata for canonical and alternate URLs to help search engines understand the relationship between similar pages — which is helpful for SEO.

For example, if you use variants to document multiple versions of your product, but want the current version to be the canonical version for SEO reasons, you can now control this in the Page options menu for your page.

You can select another GitBook page in both the canonical and alternate fields, as well as external URLs.

You’ll notice that your notification panel has a new design to make it easier to parse active and inactive notifications.

It also brings in the new colors from our recent rebrand, and adds new icons to make it clear when a notification has been checked.

If you’ve visited our website or logged into the app today, you’ve probably noticed that it’s got a new look. We’re rolling out product changes with care, as we know it’s an essential interface for your docs.

You can read more about what’s new in our announcement blog post, but here’s a quick breakdown of the small changes we’ve made to the app to bring it closer to our new branding:

Today we introduced GitBook Agent — a collaborator who works alongside your team to ensure your docs are accurate, updated, and fueling growth.

GitBook Agent can:

Head to our announcement blog post to read more about these features — and what powerful upgrades will be available soon.

We’ve introduced a new change requests screen that brings every update across your organization into one clear, centralized place.

It’s built for speed and focus — making it easier to navigate, filter, review, and ship docs updates efficiently. You can see a list of change requests with powerful filtering to help you find precisely the ones you need.

And when you open a change request, you’ll see all the information related to it in one place — including the title and description, participants, reviewers, and even all the changes rendered in diff view.

There’s also a new Overview screen for individual change requests within a space that uses the same format to make reviewing changes easier than ever.

We’ve improved the styling and customization options for the embedded version of GitBook Assistant:

You’ll also notice a new sidebar in the embedded Assistant, which lets you switch between two modes — Assistant and documentation. More on that below.

You can now embed your documentation within your product or website alongside — or instead of — GitBook Assistant.

Users can open the panel and browse your docs as normal in the small window. And if you’re using the Assistant in your docs, that’s available in the other sidebar tab.

Embeddable docs are available on Premium and Ultimate site plans — opening up this powerful embed feature to more users.

You can now customize the questions that appear when users first open GitBook Assistant and the AI search panel (on Premium sites or sites not using the Assistant).

You can define up to five custom questions in your site’s settings screen and these will be shown to visitors when they open Assistant or AI search. If you don’t add custom questions, users will see AI-generated suggestions instead.

You can now set a shorter page link title that will appear in the table of contents — great for tidying up if you have a lot of pages with lengthy titles.

For example, if you have a page with a long title for SEO or accuracy reasons, open the page’s Actions menu and choose Edit title & slug, enable Link title, and then specify a shorter name.

This title will be used for all relative links to the page — including the table of contents, page # mentions, and the page footer navigation.

If you use Git Sync, your page will appear in the SUMMARY.md file like this:

We’ve updated the look and feel of GitBook Assistant to give your content more space, added new menus across the app with a number of improvements, and released a ton of fixes.

We’ve improved the style and layout of GitBook Assistant to make it more minimal and to give your content more space. The Assistant now appears as a full-length sidebar, nudging your content over while keeping a great layout no matter the size of your screen.

You might also notice that the styling subtly matches your site’s primary color — so the Assistant blends perfectly into your site and feels more branded to your docs.

You’ll also notice improved scroll effects on the chat stream and updated animations that are smoother and, frankly, prettier when answers appear ✨ Plus, there are now up and down buttons for easy navigation through your chat log.

Hit Ask at the top of this page or click here to try the latest Assistant improvements for yourself!

Every menu in the GitBook app has been updated with new features, improved UI and better accessibility.

First, menus now have better focus management — so you can navigate using your keyboard, and if you use your mouse, focus will remain more consistent even when selecting from submenus.

We’ve also added search to every menu. So when you open a menu, you can just start typing to narrow down the options you see.

This search also includes submenu entries. So if you open a space’s Actions menu and type ‘Share’ it will show not only the Share menu item, but also the two submenu items within it — so you can quickly find and select what you need without much manual navigation.

These changes are live now across all menus in the app, so give them a try today.

With this release, we’ve made your site logo link customizable, plus added Shiki syntax highlighting for code blocks, a new block switching menu, and more.

You can now set a custom link for your docs site’s logo in the top-left corner of your published docs.

By default, clicking the logo or site title will lead users back to the first page of your docs site. But you can now set a custom URL outside your site — or a page, section or variant on your site — to be opened instead. If your docs are part of a larger website, this can help visitors navigate back to your own landing page

To set a custom link, open your site’s Customization settings and switch to the Configure tab. In the Primary link section, add the URL you want your logo to link to.

Code blocks in the editor now use Shiki for syntax highlighting, so they’ll render much more consistently with code blocks in your published docs.

That means that your code blocks won’t just have great performance. They’ll also match the same highlight colors as in your published docs — including your site’s custom primary and semantic colors.

We’ve added a new option to our inline palette that lets you quickly switch block types with a couple of clicks.

Simply highlight some text in a block and, in the palette that appears, use the dropdown menu to select a block to turn it into. It’s as simple as that!

Earlier this year, we released GitBook Assistant — a powerful AI tool that helps your users when they’re browsing your documentation. It was our first step towards what we see as the future of documentation, where product and docs are more intelligently connected.

Now, we’re adding ability to embed the same GitBook Assistant from your docs directly into your product or website.

So your users can access knowledge from your docs — and other tools you choose to connect via MCP — without needing to switch tools. And you can improve customer success by offering them seamless, context-aware answers and suggestions. Paired with adaptive content, it’s like giving every user a personalized product expert, available 24/7.

Head to our Embedded GitBook Assistant docs to learn more about how to get started.

This is a huge step towards our goal of bringing documentation and product closer together. We’d love to hear your initial feedback as it rolls out in beta.

If you’ve added a cover image to your page, it’s now easier than ever to adjust the size to your liking.

You can use the drag handle or keyboard controls to make it taller or shorter, and you can see the percentage size of the image so you know it’s going to fit properly.

We’ve also added a crosshair to the UI, so that when you drag to reposition the cover you know when it’s perfectly centered.

Working on your content is now faster and more performant than the editing experience in Notion. We’ve been working on backend improvements over the last few weeks, and we’ve now achieved a 2x performance improvement in the editor.

Our work on performance and stability improvements continues, but we wanted to share the results of our work with you as we hit this milestone!

When you’re editing your work and select something on the page, the inline palette appears to offer you important controls like formatting, links and annotations.

With this release, we’ve rebuilt the behavior of the palette from scratch. It’ll now be more stable if you scroll when it’s open — and it won’t blink when the selection changes. Plus, we’ve just made some overall improvements to performance and moved the link palette so it now appears below your selected text, not above it.

Breadcrumbs in search results, better support for languages and versions on the same docs site, a new comments popover panel and plenty of other improvements and bug fixes.

If your site is complex — with a lot of sections or variants — sometimes it’s hard to know if search is taking your users to precisely the page they need.

To make it easier for your users to be confident about choosing a result, we’ve added breadcrumbs to search results. Now they won’t just see the page title and relevant text from the page — they’ll also see the site section, variant, and page group that it lives inside.

Search will show a maximum of three breadcrumbs — if there are more, it’ll just show the first, second and last breadcrumb, with a … truncating the space between.

If you document multiple versions of your product and also want to offer localized versions of those docs with variants, you can now do that in GitBook — as docs sites now support both translation variants and version variants at the same time.

GitBook will automatically recognize these different variant types and show a version dropdown at the top of the sidebar, a translation dropdown in the header — or both.

When there are multiple variants in the same language, GitBook shows each of those languages in the translation dropdown in the header.

Then, the variant picker in the left sidebar will show all the variants available in that language — with the first variant opening by default when you choose a language.

Adding a comment or reading comment threads will no longer open the entire comments side panel by default. You can now add and review comments using a new popover menu.

That means you can more easily add comments right alongside the content you’re editing, and check threads right in context.

And if you want to review all the comments on a page or just prefer using the side panel for feedback? You can still access it from the Comments menu in the header bar.

Improved sidebars for change requests and version history, plus search improvements, expandable code blocks and more.

This release makes it easier for you to view and filter change requests in the sidebar within a space.

First, there are new filters that let you discover change requests you’re involved in more efficiently. For example, you can find change requests based on their creator or participants — or just see those that are awaiting review. Which means in a couple of clicks you can see all the change requests awaiting your review.

The top of the sidebar also shows a few shortcuts to some of these filters, allowing you to instantly narrow down long lists of change requests in busy spaces to just the ones you need.

Search has had a few upgrades with this release, making it easier for your end-users to find what they need:

You’ll now see a specific time and date next to each entry in the version history panel, making it easier to find the version you want when browsing back in time.

Talking of going back in time, we’ve also improved the rollback confirmation message, to make it clearer what will happen.

Finally, we’ve fixed a bug that would reload the entire page when navigating between entries in the version history — now only the content of your page will refresh.

You can now choose to make code blocks collapsed and expandable in your docs — perfect for when you have long code blocks that take up a lot of vertical space.

In the editor, simply open the block’s Options menu and enable Expandable. The block will show the first 10 lines of code, with a button to expand to show the rest. Here’s how it looks in practice!

Quickly switch between paragraphs and headings, duplicate blocks with a tap, add colored icons to your page and more.

We’ve added a few new keyboard shortcuts that let you quickly switch a text block between paragraph, H1, H2 and H3. Simply click anywhere in the block you want to switch and hit one of these shortcuts:

We’ve been using it while writing this changelog and it’s great — especially when you forget to hit # at the start of an empty line and you want a header block.

One more neat shortcut to speed up your editing workflow: you can now duplicate any block by either hitting ⌘ + D (on Mac) or Ctrl + D (on Windows), or by holding the Alt key and dragging.

If you use the shortcut, a duplicate of your active block will appear below. If you drag, you can place your block anywhere you like on the page.

And of course, it works for more than one block as a time, too — so you can select multiple blocks and duplicate them all with a quick tap.

You can now select a color for inline icons when you add them to your content

This is great if you want to attract attention to certain parts of your page content — or if you just want an inline icon to match the color of your text .

There are six colors to choose from — and if your space is published on a site, you can also choose the primary and semantic colors for the site to align your icon perfectly with the surrounding text.

To change the color of the icon (or choose a different icon from the picker), simply right-click it in the editor.

We now support exact phrase matching for internal search within GitBook.

If you want to find an exact phrase within your docs without bringing up similar matches in your search results, you can now add quotation marks around your text. Remove the quotation marks and the search will work the same way as before, highlighting close — but not exact — matches.

Migration and import improvements, searchable reusable content & API specs, and a bunch of other improvements and bug fixes.

This month we’ve improved our import and migration tools.

First, we’ve tweaked the UI copy on the import page to make it clearer that you can easily import your content directly from other docs platforms by simply pasting the URL of your current docs into GitBook.

We now also support .docx imports, making it easier to migrate your knowledge from Microsoft Word docs directly into GitBook. And we’ve added new imagery to the import screen to make it easier for you to find the option you need (and just make the UI look nicer).

We’re still working on making import and migration to GitBook even simpler, so stay tuned for more.

We’re currently rolling out a new search backend that also indexes reusable content and API specs, making them easier to find when searching your content. We’re currently running through the reindexing process for every GitBook organization. Once that’s complete, we’ll start enabling it for all organizations.

We all know how blank page syndrome can mentally block you when working on something new. To help you get started in an empty space, we’ve added some quick actions that let you instantly add a heading, image, hint, expandable or code block to an empty page with a single click.

We hope that this will kickstart your creativity while you’re working on new content — and we have more ideas to help with this that we’ll talk about soon.

Image blocks are great for showing off your product, but sometimes the image can blend with the background of your site, potentially confusing users.

To combat this, you can now add a frame to image blocks to give your images a consistent look and visually separate them from their surrounding content.

To add a frame, hover over the image, open the Options menu and enable the With frame toggle.

Here’s how framed images look in published docs:

When leaving feedback on a change request or page, we noticed that the comments panel could sometimes get a little long, with full threads displaying by default.

To combat this, we’ve removed threads from the full comments panel. Now, a button below the comment will show if it has any replies, and clicking the comment or the button will open the thread full in the side panel.

You can also click the new Expand side panel button to make the panel larger — perfect for longer or more detailed discussions.

We’ve added nested group support for site sections, allowing you to create hierarchical navigation — plus a few other improvements and fixes.

Support for nested section groups is here! You can now add multiple section groups within a section group and give them all a title and icon. You can even mix sections and nested section groups together — the sections will display in a separate area within the group menu.

We’ve also made some small quality-of-life improvements to the section header. They include a new scrolling system that adds faded edges and scroll buttons when your sections are wider than the container, and some fixes that make sections and groups more responsive and better positioned.

You may have noticed a new toolbar that appears when you’re viewing your live docs site, or when viewing a change request preview in its own tab. This new toolbar gives you quick access to useful options with a click — and you can minimize it if you don’t need it.

In a change request preview, the toolbar lets you quickly leave feedback on the change request, view the live site, view the change request in the GitBook app or jump to the editor. This toolbar is only visible to people viewing the change request preview.

A similar toolbar now also appears on you live docs site, only for members of your organization who are logged into GitBook. So if you or a teammate visits your live site, you’ll see the toolbar and can quickly jump to the docs in GitBook to change settings, customize the site, check the insights or edit the content.

We’ve been working on improvements to the review flow to take advantage of the new side panel we recently launched.

We’ve tweaked the icon for adding reviewers from a cog (which took inspiration from GitHub) to a plus + icon — which makes it clear that it lets you add more reviewers.

We’ve also added a new system that marks previous reviews as outdated when you request a new one — or when you add a new review to a change request you’ve already reviewed. Plus, we’ve added a button that lets you re-request a review.

You can now MCP servers so AI tools can interact with your docs, plus we’ve added new controls for users searching your docs, improved the page outline, and more.

GitBook can now automatically create an MCP server for your documentation.

When enabled in your site’s customization options, you give your users the option to quickly copy a link to your MCP server and connect it to other tools. By doing this, your users can access knowledge from your docs in whichever platform they choose to connect to.

For example, if your user adds your docs MCP server to VS Code, they could quickly answer questions or add information from your docs into their coding environment via calls to the MCP server.

You can enable or disable this this in your site’s Customization > Configure menu, under Page actions. Once enabled, users can quickly copy a link to your docs MCP server from the Page actions menu and paste it into configuration sections on other platforms.

We’re adding this to our extensive list of other AI documentation optimizations — including llms.txt and llms-full.txt, easy Markdown page exports, and quick options to open pages in ChatGPT or Claude.

We’re adding a new way to control search scope on your docs site.

Before, users could only choose the search scope if your site used variants for things like localizations or versioned docs. Now, your users can also choose which site sections to search within.

By default search will always show the best match — which is the user’s current variant and the default variant of every other section. They can choose to only search in your current section, or broaden the search to include all variants across alls sections.

No matter what, GitBook will automatically show the right set of buttons to make it as easy as possible for your site’s visitors to find what they need. For example, in our own docs we only show two buttons — because we have no variants.

It’s also worth noting that we no longer include language variants in the search scope. We assume most users won’t want to search multiple languages, and results in other languages can be confusing and take up space in the results section.

We’ve made some small but useful improvements to the page outline in our editor.

First, we’ve separated the On this page title from the outline itself and added an icon to make it easier to find. Plus, the title now stays sticky, even on long pages with lots of sections.

We’ve also improved the scroll behavior for longer pages. If the page outline is scrollable, it stays in sync with the page’s scroll position, keeping the active item at the top as you scroll.

We think this will make scrolling through your content — especially on longer pages — much easier.

New ways to control when change requests are merged and by whom, plus improvements to localization support, change requests and more.

With this release, we’ve introduced merge rules for change requests.

Merge rules let you define specific requirements that must be met before a change request can be merged. You can set rules within each individual space, or set rules that apply across your entire organization, which you can then override within a single space if needed.

We’ve made it easy to configure with a bunch of presets to match your team’s requirements — from requiring the change request to have a subject, to requiring review from specific members. You can combine rules in any way you like to build more complex workflows, as well as write dynamic expressions using the same language as for adaptive content.

When a change request hasn’t met all the merge requirements, the Merge button is disabled and a tooltip explains why it can’t be merged.

We’re rolling this out starting with early access users today. It will be available for everyone on the Pro plan soon. This feature has been requested a lot recently, so we’re super happy to ship it!

If you’ve used translations to localize your site into different languages, we’ve improved your users’ experience when browsing your docs.

A new language picker now appears in the top-right of the screen, allowing site visitors to select their preferred language — and that language will be maintained when navigating between site spaces and within search results.

We’ve also added language options to the Structure section of your docs site settings, allowing you to quickly and easily select the UI language for your docs site as well.

Change requests just got more powerful, with a new sidebar that lets you add a description and easily view and add reviewers.

Open the Overview sidebar in a change request and you can see its status, quickly copy a link to it, add a description and manage reviewers. The UX should be familiar to anyone who uses GitHub.

This will become especially useful with the upcoming launch of Docs Agents, but it also allows you and your team to add more context to change requests and more easily manage your review flow — especially when paired with merge rules.

You can now vertically align content in a column block. It’s ideal for creating centered or bottom-aligned content — such as when building landing pages or adding context to an image.

You can now choose more display options when it comes to card images.

Previously, images would automatically be cropped to either 16:9 or 1:1 depending on your readers’ screen size. But that meant your images could sometimes be cropped incorrectly, and portrait images would never display in full.

Now, you can choose between three options:

Introducing an all-new, super simple way to localize your docs and maintain the translations — plus smaller improvements to Assistant, better LLM-ready docs and more.

You can now automatically localize your entire docs site into 36 languages at the click of a button using our new Translations feature.

Translation uses AI to automatically translate your docs content into whichever language you choose — and will automatically update those translated versions of your docs whenever you make a change to the primary language version.

Simply choose the space you want to translate, select the source and target languages, and let AI do the rest. You can add specific instructions, such as a tone of voice or writing style, right from the modal. And you can also add a Glossary for individual languages if there are certain words or phrases that you want to be translated in a specific way across all your translations.

Once created, these translated spaces can be easily added to your docs as a variant, and any time you make a change to the original source space, the translated version of the space will auto-update following the same instructions and glossary.

That’s localization, simplified. Find out more in our docs!

After GitBook Assistant’s launch a few weeks ago, we’ve been making a bunch of small refinements to the way that it answers questions and helps your users.

First, we’ve upgraded the model, allowing for faster answers and more optimized outputs. We’ve also refined the prompt even further, which means users will get better, more accurate answers with better references.

Plus, we’ve added new auxiliary prompts to improve the quality of the recommended questions and the follow-up questions that appear in the chat after each response. You should notice that the recommended questions are shorter and more interesting, while follow-up questions will be more on-topic than before.

We’ll have some other, larger improvements for Assistant soon — including new ways to integrate it into your product. Stay tuned!

We’ve added an interface localization option for the Russian language in the published docs interface. When enabled in your site’s Customization menu, the interface of published docs will be translated into Russian.

Thanks to Rex Gratidian for contributing this localization. If you want to contribute to improving GitBook’s published docs, please head to our GitHub repo to find out more!

We’ve made a big improvement to the way our API returns Markdown for a page, so that it now outputs the content of reusable blocks and OpenAPI blocks just like other content.

This is super important, as the .md version of a URL is useful for LLM ingestion — so making sure all of your docs are LLM-friendly is vital. Now your GitBook docs are super LLM-ready, right out of the box.

You can now apply a light and dark mode image to any card — just like other images in GitBook.

To do this, open the Card options menu and choose Cover > Edit cover > Add cover for dark mode. The correct cover image will show automatically depending on the user’s settings.

We’ve also added the option to create cards that only feature a cover image. So you can remove all other fields within a card and simply show a grid of images, if you like.

We’ve been working on a ton of smaller improvements across the editor, including: