# 24 June: Performance upgrades, llms-full.txt and .md support, text alignment and more

## ✨ New and noteworthy

### Your docs site just got faster

<figure><img src="https://2672413337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPGZZo1PCN4rYgFLPD8Cl%2Fuploads%2FUEn9DZrfjU6RiIhTfgoP%2FPerformance%20LLMs%20.Md.png?alt=media&#x26;token=832a7e74-d732-4959-bf4f-01fd53b32742" alt="Three icons representing speed, llms-full.txt and Markdown file support coming to GitBook, all showing on a pale background"><figcaption></figcaption></figure>

Over the past few weeks we’ve been slowly rolling out a new platform for our public docs. It’s faster, more performant, and it prepares us for [our future plans regarding adaptive content](https://www.gitbook.com/blog/coming-soon-adaptive-content).

The great news is that **this new, improved platform is now live for everyone**.&#x20;

We rolled this out slowly because we handle 150 million requests on docs hosted by GitBook every day, and each one makes multiple requests to our API. The slower rollout meant we avoided downtime caused by overloading the API with requests, and means we can now optimize how we generate pages to improve loading times.

That means your users will get improved performance in your docs, and there are a few other benefits as well…

### llms-full.txt and .md support for LLMs&#x20;

Our new docs platform means [your docs now automatically create an llms-full.txt file](https://app.gitbook.com/s/NkEGS7hzeqa35sMXQZ4X/publishing-documentation/llm-ready-docs#llms-full.txt), which includes all of the content on your entire docs site.&#x20;

[llms-full.txt](https://www.gitbook.com/blog/coming-soon-adaptive-content) is a new proposed standard for making web content available in text-base formats that are easier for LLMs to process. You can access the `llms-full.txt` page by appending `/llms-full.txt` to the root URL of your docs site.

The `llms-full.txt` file provides a comprehensive collection of all your site’s content in Markdown formatting. With this file, you make it easier for LLMs to efficiently discover and process your documentation content.

***

You can also now add `.md`  to any page’s URL in the browser to [see the content of that page rendered in Markdown](https://app.gitbook.com/s/NkEGS7hzeqa35sMXQZ4X/publishing-documentation/llm-ready-docs#md-pages).&#x20;

This is great for LLMs as well, which find it much easier and more efficient to process Markdown than a full HTML file with all the styling your docs site page includes.

### Add icons to your inline buttons

[Last month](https://gitbook-v2-kjgjszpj1-gitbook.vercel.app/url/gitbook.com/docs/changelog/may-2025/6-may-add-inline-buttons-to-your-docs-easy-block-selection-and-more) we added [inline buttons](https://app.gitbook.com/s/NkEGS7hzeqa35sMXQZ4X/creating-content/formatting/inline#buttons) to docs, and [last week](https://gitbook-v2-kjgjszpj1-gitbook.vercel.app/url/gitbook.com/docs/changelog/june-2025/17-june-column-blocks-inline-icons-and-a-bunch-of-smaller-improvements) we added [inline icons](https://app.gitbook.com/s/NkEGS7hzeqa35sMXQZ4X/creating-content/formatting/inline#icons). Now, we’re combining the two!

You can now add an icon to any button you add to your docs, allowing for more customization, and helping you attract more attention to your CTAs.

<a href="https://app.gitbook.com/s/NkEGS7hzeqa35sMXQZ4X/creating-content/formatting/inline#buttons" class="button primary" data-icon="book-open">Read the docs</a>  <a href="24-june-performance-upgrades-llms-full.txt-and-.md-support-text-alignment-and-more" class="button secondary" data-icon="square-arrow-up">Go to top</a>

### Center align headings, paragraphs and inline items

Want to build a polished landing page, add some more structure, or even make your docs the homepage for your entire product? That’s just got easier with alignments in GitBook.

You can now align header and paragraph blocks to the left, center or right of your page, allowing for more flexibility when you’re designing your content.&#x20;

Add centered titles to build a clean landing page. Right-align an image or some buttons as a CTA to read more. You can even combine alignments with our new column blocks and button icons to create variations on specific layouts you like. Here’s a quick example:

***

<h2 align="center">Getting started</h2>

{% columns %}
{% column width="33.33333333333333%" %}

<figure><img src="https://2672413337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPGZZo1PCN4rYgFLPD8Cl%2Fuploads%2F2fIiYdnDjObsB73rYEP2%2Fcheckout.png?alt=media&#x26;token=958d27ce-d5fa-46d0-99b2-2f668e8d0377" alt="A white globe icon on a purple and orange background"><figcaption></figcaption></figure>
{% endcolumn %}

{% column %}

### Paygrid Checkout

Get set up, connect with your current order flow, and start getting paid in minutes with Paygrid Checkout.

<a href="#new-and-noteworthy" class="button primary" data-icon="arrow-down-to-arc">Integration guide</a> <a href="#new-and-noteworthy" class="button secondary" data-icon="microchip">API Reference</a>&#x20;
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column width="66.66666666666666%" %}

<h3 align="right"> The Paygrid SDK &#x26; API</h3>

<p align="right">Discover our SDK and APIs and explore how you can connect Paygrid to your platform to deliver even more functionality</p>

<p align="right"><a href="#new-and-noteworthy" class="button primary" data-icon="screwdriver-wrench">Explore the SDK</a> <a href="#new-and-noteworthy" class="button secondary" data-icon="microchip">Payments API</a> </p>
{% endcolumn %}

{% column %}

<figure><img src="https://2672413337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPGZZo1PCN4rYgFLPD8Cl%2Fuploads%2F1PmjiQCw79aiTwOsk0Ip%2Fapi-image.png?alt=media&#x26;token=976d5ba0-4033-4ef0-bbb2-1135fa14bccf" alt="A white API icon on a purple and orange background"><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

***

### Select all just got better

When you hit <kbd>⌘</kbd> + <kbd>A</kbd> (Mac) or <kbd>Ctrl</kbd>  + <kbd>A</kbd> (Windows) to **Select all** within certain blocks, GitBook will now first select the contents of that block. You can hit the same keyboard shortcut again to select all the content on the page.&#x20;

The blocks that use this logic are tab, stepper, code, column and hint blocks.

<details>

<summary>Improved</summary>

* We’ve improved page position and selection when switching between pages. You’ll now jump back to the place on the page you were last and any selected content will remain selected, allowing you to jump quickly between pages to check details without needing to scroll.&#x20;
* We’ve added heading options (H1/H2/H3) to the top level of the **Block options** <picture><source srcset="https://2672413337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPGZZo1PCN4rYgFLPD8Cl%2Fuploads%2FTz4cibInUfu2cb005Na8%2Foptions-dark.svg?alt=media&#x26;token=0849b16e-a06a-46b5-8b68-ed3c14ffaf3f" media="(prefers-color-scheme: dark)"><img src="https://2672413337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPGZZo1PCN4rYgFLPD8Cl%2Fuploads%2FGSVJN7uZvFaa8D204fO5%2Foptions-light.svg?alt=media&#x26;token=12cbb65e-c311-4395-808e-8ca11a0db126" alt=""></picture> menu for paragraph and heading blocks to make it easier to switch between different headings when creating or editing docs.
* When you hit <kbd>⌘</kbd> + <kbd>A</kbd> (Mac) or <kbd>Ctrl</kbd>  + <kbd>A</kbd> (Windows) to **Select all** within some blocks, GitBook will now first select the contents of that block. You can hit the same keyboard shortcut again to select all the content on the page. The blocks that use this logic are tab, stepper, code, column and hint blocks.
* We’ve made it easier to apply for the Community plan through your site’s settings. You can now apply for the plan directly in the settings screen, and it offers a dedicated space for Community plan users to submit their site for ads approval.
* When you create a new page, the focus will immediately be on the title. It’s a small change, but it should improve your editing experience when you add new pages to your docs!
* Fields within cards now have an **Actions button** <picture><source srcset="https://2672413337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPGZZo1PCN4rYgFLPD8Cl%2Fuploads%2FkixcrcbwaIFBTlO0PGzx%2Factions-dark.svg?alt=media&#x26;token=cf2d0f65-ce2b-4862-96ef-c0cb118bd456" media="(prefers-color-scheme: dark)"><img src="https://2672413337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPGZZo1PCN4rYgFLPD8Cl%2Fuploads%2Feau6xpR5czwHgUx2Fx2I%2Factions-light.svg?alt=media&#x26;token=264689bb-f225-48fc-b8e5-d64dd9d7966f" alt=""></picture> at the end of each field, allowing you to complete actions like adding or removing entries or deleting the field.
* In published content, you can now collapse page groups when browsing pages within those groups, and when your click between the parents the page you previously had opened will automatically open without the parent expanding. This should help save vertical space in the sidebar

</details>

<details>

<summary>Fixed</summary>

* Fixed a crash that could happen to the comments side panel if the user tried to open it without having commenting permissions.
* Fixed a bug that meant GitBook AI would sometimes process text in the wrong order when rewriting a group of blocks.
* Fixed an issue that was causing broken links to API specs in GitBook when you set up Git Sync. Now you can properly link to API specs when your content is synced to GitHub or GitLab.
* Fixed an issue that meant the wrong users could sometimes be shown as merging a change request. Now, the person who merges a change request will always be shown in the version history.
* Fixed a bug that prevented users who had been given edit access at a collection level to create spaces within that collection.
* Fixed a crash that could happen when a number field in a table was null or undefined.
* Fixed a bug that caused some jumps in the editor.
* Fixed a bug that meant a toast saying “Uploading file…” would sometimes never dismiss and remain on the screen.
* Fixed a bug with drawing blocks that meant they wouldn’t update after an edit. Also fixed a separate bug that meant copying and pasting a drawing block would sync them so updates to one would sync to the other. Now they are treated as separate blocks.&#x20;

</details>

***

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](https://github.com/GitbookIO/community) to join the discussion.
