The State of Docs Report 2025 is live! Dive in and see why docs matter more than ever:
Read the report
PricingLog inSign up

17 June: Column blocks, inline icons and a bunch of smaller improvements

We’ve added a new block type — columns — plus inline icons, a better site structure management experience and more

✨ New and noteworthy

Columns: a new way to display your content on a page

Introducing column blocks!

You can use column blocks to add two blocks on your page, side-by-side. It means you can combine two of almost any block you like alongside each other to create some powerful combinations

For example, you can combine an image, some text and a few buttons to build a nice block for a landing page:

The Paygrid SDK & API

Discover our SDK and APIs and explore how you can connect Paygrid to your platform to deliver even more functionality

Explore the SDK Payments API

Or you could add some extra context to your code blocks, diagrams or other content within a guide or docs page:

Notes

  • Replace 'your-api-key-here' with the key found in your dashboard under API Settings.

  • Use 'sandbox' for the environment if you're testing in a non-production setup.

  • This client instance will be used in all subsequent API calls in your integration.

// Step 1: Initialize the client with your API key
import { PaygridClient } from 'paygrid-sdk';

const client = new PaygridClient({
  apiKey: 'your-api-key-here',
  environment: 'production',
});

When you add a column block, you can add content to either side of the content by hitting / and choosing the block you want to add from the palette.

You can also adjust the width of the two columns using the grabber in the centre of the block. Drag it left or right to adjust the interval of the column divider — the column widths will adjust automatically.

Add inline icons to your docs content

We’ve added a new inline element that you can use in your docs — icons!

You can now add icons anywhere on your page, giving you more options when create titles, lists and much more. Head to the docs to learn more.

A simpler way to manage your site’s structure

This week we’ve improved the Structure section of your site settings, making it easier to change settings for individual site sections.

You can now see all of your site sections and groups on the left of the menu, and click on any option to view its options. On the right-hand side, you can edit options like the section’s title, icon, description and slug.

More context when Git Sync encounters issues

Before, when Git Sync encountered an error, the message that appeared in GitBook didn’t give much context about the issue.

We’ve improved the messages — they now include more information about the error so you can solve it before you retry your sync.

Improved

  • We’re renamed visitor authentication throughout the app and our docs — the feature is now called ‘authenticated access’. This new name better reflects our approach to authentication as we prepare for adaptive content.

  • We’ve revamped the dialog screen when creating new spaces — to add new content or import existing docs to GitBook much easier.

  • You can now remove reviewers after you request a review for a change request. Simply open the Overview side panel in your change request to see the list of reviewers, then open the Actions menu and choose Remove reviewer.

  • We’ve improved the way that you edit and handle inline buttons in the editor. You can now double-click or right-click to edit the button’s settings, and doing so will open a new modal that makes it easy to change the settings in one place.

  • We’ve also simplified the dialog that pops up when you publish your site, to give you a nice big view of your published site and a link to visit it.

Fixed

  • Fixed an issue where space-level integrations were shown on the site screen (and vice versa), which could lead to errors if you selected them in a place they shouldn’t be.

  • Fixed a visual bug with the redirects modal that caused a drop-down menu button to appear wider than the modal when choosing a destination space with a very long title.

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?