27 March: Open-sourcing our published documentation

You can now contribute and suggest improvements to GitBook to make published documentation even better

✨ New

  • We’ve opened our repository for the published documentation side of GitBook, so you can now contribute. Suggest improvements, submit bug fixes, translate the UI into other languages and more — it’s all possible! Head over to our contribution guide to find out more. And if you want to discover more details about this huge development in the way we make GitBook, head to our blog post!

  • We’ve partnered with Scalar to add a Test It button to OpenAPI blocks in your published documentation. Clicking Test It will open up an integrated API client, where you can add headers, cookies, variables and more — before sending the request to test your API live.

➕ Improved

  • You can now press Tab when using block selection on multiple blocks — such as lists — and they’ll indent one step.

  • We’ve improved the loading time for published spaces that include a lot of files — things should now be much speedier.

🔧 Fixed

  • Fixed a styling issue for grouped icons in search results.

  • Fixed some issues with emoji placement and color bleeding.

  • Fixed a bug that removed the hint block when adding an unorganized list and then hitting Enter to start a new block.

  • Fixed an issue with text wrapping in tab titles and table cells.

  • Fixed an issue with visitor authentication that could occur when setting a token without an expiration time.

  • Fixed an issue that prevented the insert palette opening when typing a / in the editor using Firefox.

  • Fixed some caching issues with published docs that could cause a long delay before updated content appeared.

  • Fixed some issues that were causing unnecessary rate limiting errors and CAPTCHAs for published content.

  • Fixed an issue that prevented you from exporting the content of a change request or a previous revision as a PDF.

  • Fixed an issue that was causing links between published spaces in published collections to break.

  • Fixed some issues that caused some anchor links with upper-case characters to point to the main page URL rather than the section.

  • Fixed an issue that could cause the editor to re-render when editing.

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.

Last updated