4 February: Completely revamped insights, a better header bar and more

We just shipped a huge improvement to your site insights, along with a new header bar to make space and site management easier

✨ New and noteworthy

A huge upgrade for site insights

We’ve just shipped an enormous update for site insights. It now offers a lot more data points, new visualizations, and a whole new section to make it easier than ever to track your docs site’s effectiveness.

First, insights now live in their own dedicated tab in your site’s dashboard. You can see a top-level overview of your insights on your main dashboard page, with a globe that shows recent views in the last hour by location.

Your site dashboard will now display a top-level overview of your insights, with a spinning globe highlighting recent traffic.

Click into the Insights tab and you’ll get tons more information about your site analytics. You can see traffic, popular pages, user feedback, search and Ask AI data, and data about how users are using any OpenAPI endpoints you’ve added to your docs.

In the Insights tab you can select different data sets on the left, and scroll to see more information about each one.

You’ll see a graph on each page to visualize the data, and can add filters or group your data to view specific ways. For example, you could look at search data for a specific site section, or filter your traffic data by country, device, browser and more.

Add filters or group data using chosen parameters to view information in different ways. You can hover your cursor over the graph to see data for a specific time.

By combining these filters and groups, you can drill down in to precise analytics data to track the events that you are important to you. And because our insights data is on-site, straight from the source, they’re incredibly accurate.

The new insights are available now — although the Links and OpenAPI sections are only available on Premium and Ultimate sites.

An all new space and site header

You probably noticed that the header bar in the GitBook app has changed this week, with new features and a more compact design.

The new header combines the old header and sub-nav bars into one, and makes it easier to switch between different functions whether you’re in a space or managing your docs sites. The bar’s layout stays consistent across spaces, change requests and sites — while individual controls will change to show what’s relevant.

The new space header is more consistent between different parts of the GitBook app, but will adapt depending on your needs.

Tabs make it easy to switch between different views, which is particularly useful in change requests — where you can quickly view changes or preview your edited content. It’s also great in your docs site dashboard, as it makes it easier than ever to switch between customizations, insights, settings and more.

Improved site colors and tints

We’ve just released a substantial change to the way we generate color palettes in docs sites:

  • A better color palette based on your chosen colors We now define color in terms of perceived LCH instead of RGB values. And we assign a function to each of the shades in the palette, so colors are used more consistently and always work well with each other.

  • Better color accessibility – Thanks to guaranteed accessible color contrasts, your colors will be more accessible no matter which values you use.

  • An upgrade for tint color – When enabled, the tint color of your site now tints every single element on the page, rather than just the background.

An example of how tints will now work, with changes affecting all of the content on your site — courtesy of Keycloakify.

You may notice some small visual changes across your site, but they will be minimal. If you have enabled the new Tint setting in your site’s Customization section and selected a strong primary color, you’ll see a more pronounced change. You can see the changes on your site right now.

  • If you enjoy the bold look, then set (or keep) your tint color to your primary color or another strong color. We’ll mix in that color everywhere and it’ll stay vibrant in places where it can be.

  • If you’d rather tone it down a little, then try setting your tint color to a desaturated shade. It’ll contrast with your primary color in a more subtle way.

Improved
  • We’ve updated the highlight colors in the app and published content. Which means highlighted text like this, or like this, should look a little nicer and more muted in both light and dark mode.

  • We’ve made it easier to visit a linked site (or the site dashboard) directly from a space. You can now open the space’s Actions menu and choose Site settings or Visit site to quickly open those options in a new tab, without leaving your current content.

  • It’s now easier to remove a site section or variant from a site within the Settings > Structure section of your site dashboard. Rather than having to open a modal, you can now just open the Actions menu and choose Remove.

  • Sponsored sites are now open to all open source projects! If you have open source docs and want to build your docs with GitBook, the Sponsored site plan lets you access all of GitBook’s best docs site features at no cost. It displays a small, relevant ad in the corner of your documentation site, and each view generates revenue for you — turning your documentation into a source of income. You can now choose it from the site wizard when you create a new site in GitBook. Find out more on our open source page, or in our docs.

Fixed
  • Fixed a bug that could sometimes make it impossible to edit the title of a change request.

  • Fixed a bug that caused an incorrect broken link count for some change requests. Also fixed another issue that prevented you from filtering the broken link lists properly.

  • Fixed some bugs with Ask AI, including duplicated sources, duplicated recommended questions and responses sometimes being incorrectly formatted.

  • Fixed an issue that meant saving site customizations wasn’t possible when the site title section was empty.


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?