6 May: Add inline buttons to your docs, easy block selection and more

Want to add a button to your published docs? Now you can — plus we’ve made block selection easier, and made some smaller improvements and fixes

✨ New and noteworthy

Add primary and secondary buttons to your docs pages

You can now add buttons to your GitBook content, meaning you can now create calls-to-action right on the page.

Here’s how buttons look when published:

Sign up Read the docs

Buttons are an inline option — like emoji, links and inline images. You can add one to any text block, and they can link to any other content within your docs, or any external URL. Simply hit / to open the inline palette and choose Button.

Buttons come in two styles — primary and secondary. In the editor they’ll appear as black or white, but in published content they’ll use your site’s primary and color to style the primary button and a derivative (typically black or white) for the secondary color.

Click and drag to select blocks

We’ve added a new way to select blocks on your page — click and drag.

Before, you could select one or more blocks by highlighting the content within them and hitting Esc. Now, we’re adding a second option that makes it simple to grab large groups of blocks in one go.

Simple click and drag your cursor across the blocks you want to select to see the selection box. Releasing the mouse button will select all the highlighted blocks, ready to be copied, deleted or turned into reusable content.

Improved

• We’ve fixed a bug that snuck into comments that meant you would instantly jump to the block when clicking a comment, rather than smoothly scrolling there. The smooth scrolling has now been restored, so jumping between comments on a page will offer more context of where the comment is.

Fixed

• Fixed the color of highlighted selections when using the new palettes in dark mode. The highlighted option is now much more legible.

• Fixed an issue with the link palette that meant you couldn’t navigate into submenus using the right/left arrows on the keyboard — it would instead remove focus and close the palette. Now you can navigate the entire menu with the keyboard.

---

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.