25 February: New and improved hint blocks

You can now add titles to hint blocks and customize their colors for published content, plus we’ve released a number of other smaller improvements

✨ New and noteworthy

New hint block design and colors

We’re redesigned our hint blocks to give you more options when creating your docs.

The new blocks now use a smaller font size, and you have the option to add headings to them, which will appear in a colored bar at the top of the hint. To do this, simply add a heading block as the first block inside the hint block.

By default, this is how hint blocks will look in published content. The top hint in this demo does not have a title, while all the others do.

If you’re publishing your content on a docs site, you can also customize the colors of your hint blocks however you like. To do this, head to your site’s Customization menu and scroll down in the General tab until you see Semantic colors.

You can change the color of your hint blocks in published content by opening the Customization screen for your site and selecting new semantic colors. The preview on the right will update in real-time.

Here, you can set the colors for Info, Success, Warning and Danger. Once you hit Save, the hint blocks in your published content will update with those chosen colors.

Improved
  • We’ve made some improvements to the menu for inserting OpenAPI blocks on a page. It’s now easier to find and select the operations you want to add, and the colors match the operation colors on the page.

  • You can now add tables, quotes and hint blocks within an expandable block. So you can do things like this:

And this is a quote block in an expandable block.

Block types within this expandable block
Was this possible before?
Is it possible now?

Unordered list

Hint

Quote

Table

Fixed
  • Fixed the OpenAPI block syntax highlighting in the GitBook app to make sure code is properly highlighted.

  • Fixed a bug that prevented you from being able to remove a site after you removed all the spaces linked to it.


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?