> For the complete documentation index, see [llms.txt](https://docs.ultramarinastudios.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ultramarinastudios.com/theme-settings/spacing.md).
# Spacing
When customizing a new theme, we recommend starting with customizing these global spacing settings before you make granular tweaks to individual settings in order to minimize setup work.
#### Spacing scale size
This setting determines the overall spacing size and sizing of elements. This can be a quick way to create looser or tighter spacing across the theme without tweaking individual settings.
#### Vertical and horizontal grid gap
This setting controls the spacing between groups of similiar items, such as within a product grid, testimonials, blog posts, etc. This can be controlled at a desktop and mobile level.
#### Section gap
This setting controls the spacing between elements within a section, such as the distance between a section header and the content. This can be controlled at a desktop and mobile level.
#### Section padding
This setting controls the spacing at the start and end of each section. Most sections allow you to override this at a section level, so set an appropriate default first before you make any customizations This can be controlled at a desktop and mobile level.
Diagram of the grid gap, section gap and section padding settings described above
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ultramarinastudios.com/theme-settings/spacing.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
