> 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/theme-style.md).

# Theme style

Overview of Theme style preset options under the Theme settings

Pipeline provides four preset options that serve as a starting point for users to try out and unleash their creativity. These choices come with preselected color schemes, font styles, spacing, and other features. You can experiment with these styles without affecting any of your theme's content, making them useful when setting up your store for the first time.

## Overview

<details>

<summary>Settings overview</summary>

* Choose a preset theme style to apply sitewide.&#x20;

Tip: Presets will not affect your content, only theme design elements

</details>

Video walkthrough for Theme style presets:&#x20;

{% embed url="<https://www.loom.com/share/459eaab59235467890d9ab0bf5e196ac?sid=5f48bd66-2286-43bc-95ef-f421f767b16c>" %}

{% hint style="info" %}
Remember to save any settings you've already made before choosing a preset. Certain elements like colors and theme settings will be replaced when using a preset. None of your content will be changed.&#x20;
{% endhint %}


---

# 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/theme-style.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.
