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

9 September: Merge rules, improved language selection and more

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

✨ New and noteworthy

Merge rules

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!

Improved language selection

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 request descriptions

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.

Vertical alignment in column blocks

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.

Fit and fill options for card images

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:

  1. The image crops to 16:9 or 1:1 as before.

  2. The image stretches to fill the entire box.

  3. The image displays in full within the constraints of the box, with your primary color filling any background space.

Improved

  • We’ve made it easier to invite new members to your organization in bulk. Simply add the email addresses of the users you want to invite to the box, separated by commas, to add up to 100 users at a time.

  • We’ve tweaked the search results for localized versions of published docs. Now, if a user is viewing your docs in another language and they use the search bar, instead of seeing results in both their selected language and the site’s default language, they’ll see results only in their selected language when available.

  • If you link a new organization to your email domain, GitBook will now automatically use the email domain’s favicon as the organization’s logo. And when you create your first site in that organization, GitBook will automatically use the same favicon as the site’s icon.

  • The Export as PDF and Edit on Git options now appear in the Page actions menu on your published site. And the settings to toggle them on and off are now in Customization > Configure along with the other Page actions options.

  • We’ve made a few small improvements to the page outline.

    • First, titles within Stepper blocks will now appear in the page outline, allowing users to jump quickly to the step they need.

    • Second, we’ve fixed a bug that meant links in H1, H2 and H3 headers wouldn’t appear in the page outline. Now the full heading will appear in the page outline, including words that are links.

    • Finally, we’ve added column headings to the page outline, so that all headers will appear in the page outline.

  • We’ve added an Editor tab to your site’s dashboard, which instantly navigates you to the default site space ready to start editing.

  • If you use OpenAPI blocks, GitBook now renders OpenAPI schemas properly as JSON in the Markdown version of a page.

  • We’ve improved the billing page in the app to make it easier to see what’s included in your subscription and to make changes.

  • Headers now support bold and italic, allowing for more formatting options.

Fixed

  • Fixed a bug that meant links in H1, H2, and H3 headers wouldn’t appear in the page outline. Now the full heading will appear in the page outline, including words that are links.

  • Fixed a bug that prevented you from adding images to a table cell.

  • Fixed a bug that meant holding Shift and clicking in a code block would select the entire block, instead of selecting the text within the block. Now it works as expected.

  • Fixed a sizing issue that meant inline mentions that included non-square icons (such as ⌨️) were aligned too close to the adjacent text.

  • Fixed an issue where Git Sync progress percentages were exceeding 100, because no matter how hard it tries, Git Sync cannot realistically give 110%.

  • Fixed a bug that meant files you renamed in your Git repo didn’t sync into the GitBook editor.

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?