Product updates
Published:
14 May, 2025
New in GitBook: Global reusable content, auto-updating API docs, and much more

AI summary
GitBook has released a major update focused on enhancing documentation efficiency through auto-generating OpenAPI reference docs and enabling global reusable content across an entire organization. These improvements are complemented by a redesigned, space-saving sidebar and various editor upgrades, including interactive buttons and enhanced block selection capabilities.
Last month, we told you about the massive number of updates weโd shipped since the start of the year. We donโt want to leave it so long between updates again, so hereโs another!
All of these updates aim to make your documentation more dynamic, easy-to-maintain, and user-friendly. From auto-updating API references to a redesigned sidebar, hereโs a roundup of everything thatโs new โ remember to check out the changelog to see all our updates as they happen!
Auto-updating API reference docs
We know that two of the biggest challenges when documenting APIs are updating the docs when the specification changes, and auto-generating the docs in the first place.
Thatโs why weโve created a new way to generate API documentation from an OpenAPI specification in seconds. The new OpenAPI section in the sidebar lets you add your spec from a URL, upload it as a file, or use the GitBook CLI.

Once added to your organization, itโs super easy to use the spec to generate OpenAPI blocks โ or a complete API reference โ in any space. If you add your spec using a URL, GitBook will automatically check for updates every six hours. Any changes will be pushed to your API docs right away.
This is the first use case for a new method weโre working on to create documentation from existing information. Weโll talk about this more โ for OpenAPI, but also for other use cases โ next week. Stay tuned!
Global reusable content
Reusable content can now be used across your entire organization. So you can add any reusable content to any page, in any space in your org โ no matter where it was originally created.
Before, reusable content was locked to a specific space. With global reusable content, you can keep information consistent between multiple published spaces without risking instances getting out of sync.

The process for adding reusable content hasnโt changed. Just hit the / on any empty block and choose Reusable content from the menu. You can choose content from your current space, or browse through all your reusable content across all your spaces.
This is something we had a lot of requests for, so weโre excited to hear what you think. Weโll continue working to improve the experience of using reusable content globally โ hopefully weโll have more to share soon.
New sidebar: more space, less clutter
This week we shipped a huge sidebar upgrade that shows 30% more content and can be accessed easily, even when the sidebar is collapsed.
The new sidebar moves a lot of the options that sat at the bottom of the window into the top organization menu, freeing up more space for your content. Itโs also more compact, so you can see a lot more in the same space.
Itโs also resizable, so you can change the width to fit your workflow. And thereโs a new collapsed mode โ simply drag it off the screen to hide it entirely. Itโll appear on hover, and hide again when you move your cursor away. So you can quickly access all your content, without expanding it and collapsing it manually every time.
Plus, the docs site section has done away with the unnecessary nesting, making it quicker and easier to navigate to the site and space you want.
Add button blocks to your docs
Weโve added a new option to docs: buttons! You can now add interactive buttons directly to your documentation pages โ perfect for guiding users to sign-up pages, external resources, or other important actions. Plus, they add another layer of interactivity to your docs.
The editor improvements continue!
Our dedicated editor squad has been hard at work shipping a bunch more improvements and fixes over the past few weeks. Hereโs a quick breakdown of whatโs new in the editor:
Better OpenAPI and code block designs
Weโve made some tweaks to the design of API blocks and code blocks in published content. First off, weโve tweaked the OpenAPI blockโs layout to make it more consistent and easier to parse. Weโve also improved object accordions and added new schema alternatives separators including anyOf, allOf, and oneOf.

But thatโs not all! Youโll also notice updated colors for API and code blocks in your published documentation. Theyโll now use your siteโs primary, tint and semantic colors to style the code โ so if youโve set those colors to match your brand, your code will match those colors too.
Plus, your site will now automatically show a high-contrast version of those colors when requested by a userโs browser.
Click and drag to select blocks
Weโve added a new way to select blocks on your page โ click and drag.
Simply click and drag your cursor across the blocks you want to select to select the highlighted blocks. Itโs a fast and easy way to select blocks you want to copy, delete or turn into reusable content.
New palettes
Another small UX improvement โ better palettes. The new palettes are more visually aligned with other parts of the GitBook app UI, and generally look a little nicer. Weโve rolled out this design change across all the menus in the app, and weโve also made some other improvements to the link and inline palettes.

The link palette is now sorted into link types, making it easier to find what youโre looking for. And the inline palette is now searchable, so you can add links, images, or those new buttons we talked about above more easily than ever.
Turn paragraph blocks into other text-based blocks
Until now, you could only turn text blocks into other kinds of basic text blocks. For example, you could make a paragraph block into H1, H2 or H3 headers, but that was all.
Now, you can turn a paragraph block into all kinds of other blocks. So you can make it a hint, a code block, an expandable, and many others. Give it a try!
Icons on relative links
Relative links โ that is, links to other pages within your docs โ will now appear with the pageโs icon or emoji next to the title in the editor. Before, theyโd show a space, page or anchor link icon, but this change adds a splash of identity and adds some context to your links.

Next week: A computed content deep dive
Thatโs all the biggest news from the last few weeks โ but thereโs more where that came from. If you want to read more about these updates and everything else that weโve shipped in the last few weeks, head over to our changelog.
Next week weโll be spending some time talking about our new OpenAPI feature, internalization for your documentation, and more. Theyโre all related to a new system weโve been working on in the backend โ weโll explain them in more detail in the coming days. Check back throughout next week to read more.
โ Get started with GitBook for free
โ The seven principles of great API docs and how to apply them
Share
Read more
Product updates
Get the GitBook newsletter
Get the latest product news, useful resources and more in your inbox. 130k+ people read it every month.
Accurate docs. Better answers.
Your docs are already feeding AI. Are users getting the right answers or the wrong ones?
Accurate docs. Better answers.
Your docs are already feeding AI. Are users getting the right answers or the wrong ones?
Accurate docs. Better answers.
Your docs are already feeding AI. Are users getting the right answers or the wrong ones?
Product
Create & Publish
Solutions
Resources
ยฉ 2026 Copyright GitBook INC.
440 N Barranca Ave #7171, Covina, CA 91723, USA. EIN: 320502699
Get an AI summary

The State of Docs Report 2026
State of Docs brings together insights from documentation experts from across the industry

Product
Create & Publish
Solutions
Resources
ยฉ 2026 Copyright GitBook INC.
440 N Barranca Ave #7171, Covina, CA 91723, USA. EIN: 320502699
Get an AI summary
The State of Docs Report 2026
State of Docs brings together insights from documentation experts from across the industry

Product
Create & Publish
Solutions
Resources
ยฉ 2026 Copyright GitBook INC.
440 N Barranca Ave #7171, Covina, CA 91723, USA. EIN: 320502699
Get an AI summary
The State of Docs Report 2026
State of Docs brings together insights from documentation experts from across the industry










