24 September: Nested section groups, new change request review options and more

We’ve added nested group support for site sections, allowing you to create hierarchical navigation — plus a few other improvements and fixes

✨ New and noteworthy

Nested section groups

Support for nested section groups is here! You can now add multiple section groups within a section group and give them all a title and icon. You can even mix sections and nested section groups together — the sections will display in a separate area within the group menu.

This group contains two sections displayed on the left and a nested ‘Guides’ group displayed on the right.

We’ve also made some small quality-of-life improvements to the section header. They include a new scrolling system that adds faded edges and scroll buttons when your sections are wider than the container, and some fixes that make sections and groups more responsive and better positioned.

A new toolbar when viewing your docs

You may have noticed a new toolbar that appears when you’re viewing your live docs site, or when viewing a change request preview in its own tab. This new toolbar gives you quick access to useful options with a click — and you can minimize it if you don’t need it.

In a change request preview, the toolbar lets you quickly leave feedback on the change request, view the live site, view the change request in the GitBook app or jump to the editor. This toolbar is only visible to people viewing the change request preview.

A similar toolbar now also appears on you live docs site, only for members of your organization who are logged into GitBook. So if you or a teammate visits your live site, you’ll see the toolbar and can quickly jump to the docs in GitBook to change settings, customize the site, check the insights or edit the content.

Note: The new site toolbar is not visible to anyone outside of your GitBook organization. It will not appear for your end-users when they visit your docs site.

Review process improvements

We’ve been working on improvements to the review flow to take advantage of the new side panel we recently launched.

We’ve tweaked the icon for adding reviewers from a cog (which took inspiration from GitHub) to a plus + icon — which makes it clear that it lets you add more reviewers.

We’ve also added a new system that marks previous reviews as outdated when you request a new one — or when you add a new review to a change request you’ve already reviewed. Plus, we’ve added a button that lets you re-request a review.

Improved

• We’ve added support for pasting, parsing, and formatting one-row or header-only tables. You can now create a single-row table either in the editor or in Markdown via Git Sync, and it will display correctly in the editor.

• When you highlight a URL in the app and choose to add a link to it, GitBook will now recognize the URL and auto-populate the link palette so you can quickly turn it into a link to that URL.

Fixed

• Fixed a couple of bugs with text selection in popovers — such as the change request review dialog — and the Shift + click behavior across the app.

• Fixed a bug that meant palettes didn’t automatically expand their width to show all of the copy within a list of options. Now all palettes should expand so you can read the copy for each option.

• Fixed an error that could occur when opening a preview of your primary content.

• Removed a tooltip that incorrectly said the Share button in a space could be used to publish that space as a site.

• Fixed a limitation that meant conditional {if} blocks couldn’t contain full-width content. Now they can.

• Fixed an issue that meant the bottom of the app would sometimes crop part of the way up the browser window when accessing the side panel for things like comments or version history.

• Fixed an issue with site templates that meant new sites created from a template would have broken links.

---

We’re constantly working to improve the way you and your team work in GitBook, and we value your input on features, bugs, and more. Make sure you head to our official GitBook community to join the discussion.