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

## ✨ New and noteworthy

### AI-powered, auto-updating translations are live

<figure><img src="https://2672413337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPGZZo1PCN4rYgFLPD8Cl%2Fuploads%2FT9mOdPvALz8HkKKkhAS0%2Ftranlsation-screen.png?alt=media&#x26;token=fd44ce4d-7ed3-463f-99a6-71eabacad4be" alt=""><figcaption></figcaption></figure>

You can now automatically localize your entire docs site into 36 languages at the click of a button using [our new **Translations** feature](https://app.gitbook.com/s/NkEGS7hzeqa35sMXQZ4X/creating-content/translations).

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.

<figure><img src="https://2672413337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPGZZo1PCN4rYgFLPD8Cl%2Fuploads%2Fn61pDZMgHg0LVAeIbCWP%2Ftranslation-modal.png?alt=media&#x26;token=16b4245f-85b1-429e-a96c-e2c023eb87f7" alt=""><figcaption></figcaption></figure>

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](https://app.gitbook.com/s/NkEGS7hzeqa35sMXQZ4X/creating-content/translations)!

### GitBook Assistant improvements

<figure><img src="https://2672413337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPGZZo1PCN4rYgFLPD8Cl%2Fuploads%2F4NcRJdIJiQpTVE6aGXjA%2Fgitbook-assistant-button.png?alt=media&#x26;token=e0d25561-c351-4ea5-9a4c-ae7b2069b66c" alt=""><figcaption></figcaption></figure>

After [GitBook Assistant’s launch](https://gitbook-v2-kjgjszpj1-gitbook.vercel.app/url/gitbook.com/docs/changelog/august-2025/1-august-gitbook-assistant-improved-insights-new-ai-actions-and-more) a few weeks ago, we’ve been making a bunch of small refinements to the way that it answers questions and helps your users.&#x20;

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.&#x20;

Thanks to [Rex Gratidian](https://github.com/mydarlingrex) for contributing this localization. If you want to contribute to improving GitBook’s published docs, please head to [our GitHub repo](https://github.com/GitbookIO/gitbook) 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](https://app.gitbook.com/s/NkEGS7hzeqa35sMXQZ4X/creating-content/reusable-content) and [OpenAPI blocks](https://app.gitbook.com/s/NkEGS7hzeqa35sMXQZ4X/api-references) just like other content.&#x20;

This is super important, as the `.md` version of a URL is [useful for LLM ingestion](https://gitbook-v2-kjgjszpj1-gitbook.vercel.app/url/gitbook.com/docs/changelog/june-2025/24-june-performance-upgrades-llms-full.txt-and-.md-support-text-alignment-and-more#llms-full.txt-and-.md-support-for-llms) — 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](https://app.gitbook.com/s/NkEGS7hzeqa35sMXQZ4X/creating-content/blocks/cards) — just like other images in GitBook.&#x20;

To do this, open the **Card options** <picture><source srcset="https://2672413337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPGZZo1PCN4rYgFLPD8Cl%2Fuploads%2FTz4cibInUfu2cb005Na8%2Foptions-dark.svg?alt=media&#x26;token=0849b16e-a06a-46b5-8b68-ed3c14ffaf3f" media="(prefers-color-scheme: dark)"><img src="https://2672413337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPGZZo1PCN4rYgFLPD8Cl%2Fuploads%2FGSVJN7uZvFaa8D204fO5%2Foptions-light.svg?alt=media&#x26;token=12cbb65e-c311-4395-808e-8ca11a0db126" alt=""></picture> 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.

<details>

<summary>Improved</summary>

* We’ve added URL query parameters for search (`?q=`) and the AI search/GitBook Assistant (`?ask=`). So you can add search topics or questions to a docs URL (e.g. [gitbook.com/docs/?ask=What+is+GitBook?](https://gitbook.com/docs/?ask=What+is+gitbook?)) and have the search or GitBook Assistant open automatically with a query pre-filled.
* If you’re viewing a space’s Preview and then click **Edit**, it now opens a new change request and automatically redirects you to the Editor view so you can immediately start editing. Before, it would maintain your Preview view.&#x20;
* We’ve improved the UX of the **Annotate** option in the inline palette when editing. There’s a new icon and tooltip to make the difference between annotations and comments clearer.

- We’ve improved the way that moving list items around works. Now, when you drag a list item into a new block, it will keep the same list type. But if you drag a list item into another list of a different type, it will automatically switch to that new list type.
- The site settings and insights screens now make better use of space.
- We’ve changed the way that you copy anchor links in the editor. Now, when editing a page you can edit or copy an anchor link by opening the **Block options** menu <picture><source srcset="https://2672413337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPGZZo1PCN4rYgFLPD8Cl%2Fuploads%2FTz4cibInUfu2cb005Na8%2Foptions-dark.svg?alt=media&#x26;token=0849b16e-a06a-46b5-8b68-ed3c14ffaf3f" media="(prefers-color-scheme: dark)"><img src="https://2672413337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPGZZo1PCN4rYgFLPD8Cl%2Fuploads%2FGSVJN7uZvFaa8D204fO5%2Foptions-light.svg?alt=media&#x26;token=12cbb65e-c311-4395-808e-8ca11a0db126" alt=""></picture> and choosing the **Link** option. If the page is in read-only mode, you can copy the anchor link by clicking the # to the left of the title — just like you do in the published version of your docs.

</details>

<details>

<summary>Fixed</summary>

* Fixed an issue that prevented you from making inline code bold or italic — that’s now possible again.
* Fixed a bug that hid the ‘show/hide table of contents’ button behind the header image if it was enabled for a page.
* Fixed a bug with non-default variants that would resolve incorrectly if there was a conflicting deprecated path.
* Disabled the option to turn a single line in a list into reusable content, as doing so would delete the line.
* Fixed a crash in the Insights table when navigating through pages aggregated datasets with custom sorting.
* Fixed an issue in the editor that meant cards with different lengths of content would appear at different heights in the same block. This didn’t align with the published version. Now cards will all use the same height as the card with the longest content, just like in published content.
* Fixed an issue with block selection that would happen when you selected a code block with a title.
* Fixed a bug that was causing the editor to refresh whenever you changed a page title.
* Emojis added to titles via our inline emoji picker are now listed in the ‘On this page’ section on the left.&#x20;
* Fixed an issue that meant updating site customization could result in an error message.
* Fixed a bug that meant setting a cover image for a card could do nothing, or in some cases could remove cover images from other cards.
* Fixed an issue that meant users couldn’t install integrations in the site or space screens due to missing permissions check in the backend.
* Fixed a bug that meant when deleting the last card or row in a table, the table block disappeared but the wrapper remained, which made it difficult to add new blocks to the page.

</details>

***

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](https://github.com/GitbookIO/community) to join the discussion.
