Embed GitBook Assistant, performance improvements and more

With this release you can now embed GitBook Assistant in your product or website — plus we’ve made performance improvements, added new cover resizing options and more

Embed GitBook Assistant in your product or website

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.

Adjustable page cover heights

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.

Big improvements to editor performance

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!

Improved inline palette

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.

Improved

• You can now drop images in the space between two blocks to add a new image block to the editor. Before, you had to create a new line first. Now you can simply drag your image right where you want it and boom — you’ll get a new image block.

• We’ve added a small pop-up message to tell you when there’s a new version of the app available, so you can quickly refresh to get the latest features and best performance (i.e. all the stuff we talk about in this changelog)

• You’ll notice a number of small tweaks to the sidebar and table of contents in the GitBook app that make their design more consistent. The icons and tooltips for the Actions menu are now the same, and the line height and icon size are also identical.

Fixed

• Fixed an issue that meant you couldn’t select an anchor link on the same page when updating a link in your text.

• Fixed a bug that meant selecting a link with the sidebar collapsed and then expanding the sidebar would prevent you from closing the sidebar or reactivating the editor.

• Fixed a bug that prevented you from commenting on a deleted block or page within a change request’s diff view.

• Fixed a bug that was causing an overflow problem when hovering over a link in the editor.

• Fixed an issue that meant content tokens for our published docs platform could access private API endpoints.

• Fixed a bug that meant diff view wasn’t working properly in code blocks, and checking changes could cause a crash.

• Fixed an issue that meant published content was not updating when translations were generated.

• Fixed a bug that meant a Publish button would appear on the site dashboard for published sites if they had search indexing disabled. Now the button will show the Visit button as expected.

• Fixed an issue with the preview panel in read only mode that meant clicking a link in the preview would close the preview. Now links will work as expected.

---

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.