10 January: Turn snippets into docs, change your public docs font and more

We’re making it even easier to turn knowledge into documentation in your knowledge base, adding a free customization option for everyone, and much more

✨ New

• You can now easily turn snippets into documentation pages in your knowledge base! So when you’ve saved a technical guide from a really helpful thread in your #engineering Slack channel, you can now add it to exactly the right space in GitBook, for everyone to find and use.

You can now turn a snippet into a page in your docs — it’ll instantly create the page, or automatically open a new change request if your space has locked live edits.

• You can now reference snippets in your documentation, using either the new snippets block, or using a # style mention. So even if you don’t want to turn your snippet into it’s own page, you can still point people toward it when you need to.

• We’re making it easier to set up visitor authentication for your published documentation without needing a custom backend. Instead, you can install integrations that serve as the backend for authenticating users and generating JWT tokens. We’re testing this with selected customers right now, and will open it up to all Pro and Enterprise organizations soon.

• We’ve restored Inter as the default font choice for public content, as Inter has better support for more languages than Favorit. You can switch your font back to Favorit in the Customize menu if you prefer — and we’ve made it available to everyone, no matter what plan you’re on.

➕ Improved

• You can now quickly create a snippet using the + button next to Snippets title in the sidebar.

• We improved support for lists in search results when using GitBook AI search.

• We’ve also improved the quality of suggested questions in GitBook AI search so that it uses actual content within the organization.

• We’ve updated the template screen to reflect the new brand colors.

• The Git Sync side panel will now hide while its progress model is showing.

• Comments on deleted pages now appear at the bottom of the list of comments.

• Readers in your organization can now access and read snippets too.

• We’ve updated our primary colors in the app to improve color contrast and accessibility.

• You can now edit a collection’s title and description, or delete a collection using the API.

🔧 Fixed

• Fixed an issue that caused the search modal to change widths as you typed.

• Fixed an SPI error that occurred when you submitted a change request with no reviewers.

• Fixed an issue where changing the title would cause focus to move away from the page.

• Tidied up some text inconsistencies in the app following our recent font change.

• Fixed a bug that caused a slug not to be generated properly when a Git Sync import didn’t include a SUMMARY.md.

• Fixed an issue that caused the content Change Request side panel to overflow into the header when it overflowed.

• Fixed a bug that could cause some admin rights to be overwritten when an admin visited an invite link.

• Fixed direct links to relations in the Content audit section of Insights.

• Fixed an issue that could show an error when modifying header links in published content using the Customize menu.

• Fix an issue where badly parsed math blocks could cause a Git Sync failure or an app crash.

• Fixed a bug that meant the error screen didn’t respond to light or dark mode.

• Fixed a bug that caused the footer not to show in published collections.

We’re constantly working on improving 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!