8 July: Custom code fonts, make your API spec public and more
You can now upload your own custom font for code blocks, create new sites more easily, make your API spec public and more
Last updated
Was this helpful?
You can now upload your own custom font for code blocks, create new sites more easily, make your API spec public and more
Last updated
Was this helpful?
Was this helpful?
You’ve been able to upload a custom font for your docs for a while — but now you can do the same for a monospace font for code blocks and inline code.
To change your code font, head into your site’s Customization panel and select from the Monospace font dropdown menu.
You can now choose to generate a publicly-accessible URL for your OpenAPI specification once you’ve added it to GitBook — as long as your specification is marked as public. The URL will always point to the latest version of your specification.
With GitBook hosting your spec, it’s easy to use it both to instantly generate docs, and in external OpenAPI-based tools like Stainless, Postman or others.
Head into the OpenAPI section in the GitBook sidebar and find the API you want to make public — then simply hit the toggle.
Last month we improved a few of our emails with a better design and more context about the subject — and we mentioned we’d be doing the same to more emails soon.
Well, now we have! Our emails now all use this new improved style ✨
When you create a new site, you’ll now see a dashboard that’s more tailored to what you want to do.
First, you’ll see four large options at the top to offer you different ways to add content to your site — including Git Sync, OpenAPI spec upload, and import options.
Below that, you’ll also see four site templates to help you get started with an all-new site faster by adding content to an established structure.
Finally, you’ll see a list of all your existing content within GitBook, along with a search bar, allowing you to quickly add existing content to your site and publish with a click.
These changes should make it easier to create an publish your site fast 🏎️💨
Table blocks and expandable blocks now support diff view more effectively. Before, editing any part of a table would show the entire table as being deleted and a new one created in diff view. The same went for changes in an expandable block. Now, the table or expandable shows as edited and the individual changes are highlighted within the block.
We’ve added icons to diff view to make diffs accessible for color-blind users Make diff accessible to colour-blind users.
You’ll now see a new option to visit the a published page’s live version in the Actions menu 
for individual page. This is especially useful for hidden pages that are otherwise difficult to access via URL.
We no longer show captions on image and code blocks in the editor by default. Captions added a lot of white space in the editor, meaning big gaps between content if you didn’t want to add a caption. Now they won’t appear by default, but you can add one by hovering the image and clicking Caption in the menu that appears.
You can now use keyboard shortcuts to insert new rows in tables. Hit Enter ⏎ to move down or Shift ⇧ + Enter ⏎ to move up between rows. Then hit Option ⌥ + Enter ⏎ to add a row below, or hit Shift ⇧ + Option ⌥ + Enter ⏎ to add a row above.
You can now convert H1, H2 and H3 heading blocks to other heading styles by adding # at the beginning of a row.
We’ve added a confirmation button to the annotation and Math popover when adding them inline. Your changes are saved automatically, but it helps reassure users that their changes are saved.
We now check that uploading files are compatible with inserting into GitBook before you upload them to avoid wasted uploads.
We’ve updated the Docs sites screen to make it easier to find and open your site.
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.