19 August: Auto-updating translations, AI Assistant improvements and more

✨ New and noteworthy

AI-powered, auto-updating translations are live

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!

GitBook Assistant improvements

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!

Russian language support

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!

Better Markdown support for your LLM-ready docs

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.

Light and dark card images

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.

A bunch of editor improvements

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

• More consistently centered content within the editor across all screen sizes, to stop content moving around when you open or close different sidebars in the app.

• An improved page outline which stays sticky next to the content editor. We’ve increased the visibility conditions so you’ll see it more often, simplified its logic, and added stepper blocks to the outline so you’ll see each step listed alongside other section headers.

• We’ve fixed diff view, which wasn’t showing the diffs on some smaller screens. Now you’ll see diff markers by each block that’s changed.

• We’ve also fixed a bug that meant the comments button could be cut off on smaller screens. Now it will appear as expected, ready for you to give feedback.

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.