> For the complete documentation index, see [llms.txt](https://pipeline.groupthought.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pipeline.groupthought.com/settings/theme-settings/layout.md).

# Layout

Overview of layout options under the Theme settings

Within the theme, the layout settings offer the ability to adjust multiple layout aspects using various controls.

## Overview

<details>

<summary>Settings overview</summary>

* Page width
* Grid column spacing for sections with columns
* Page spacing
* Button radius
* Animations including text scrolling, hover animations, and parallax images

Tip: The parallax setting can help you reduce image cropping when combined with the Image height setting at the section level.&#x20;

</details>

Video overview of layout controls in the theme settings:

{% embed url="<https://www.loom.com/share/a72f07ff9a2943a8b9be627f5ff72382?sid=31ff2f9b-ba09-46ff-89cd-d024c6144dcf>" %}

{% hint style="info" %}
In the video, you'll learn how to achieve zero-cropping for your images.
{% endhint %}

<details>

<summary>Reference for reducing image cropping</summary>

* Set the section height to the "Image height" setting. &#x20;
* Turn off animations for Parallax images in the Layout settings.

</details>


---

# 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://pipeline.groupthought.com/settings/theme-settings/layout.md?ask=<question>&goal=<user_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.