> For the complete documentation index, see [llms.txt](https://docs.atloss.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.atloss.de/en/theme-configuration.md).

# Theme configuration

The theme configuration offers you a wide variety of settings for your shop. All adjustments relate to the [storefront](https://docs.atloss.de/en/academy/technical-terms/storefront.md).

Once you have successfully completed the [setup](https://docs.atloss.de/en/setup.md), the theme will be available in the administration panel on the left-hand side under “Content > Themes.”

Alternatively, you can also access the theme configuration directly via your sales channel, which is also located on the left-hand side of your administration panel. Once there, go to the “Theme” tab. Now click on “Edit theme” to access the configuration overview.

<figure><img src="https://content.gitbook.com/content/33GKvYy9I8ydtLM82CBS/blobs/1GoOJo5Ez6B42HacdT8H/theme-konfiguration-uebersicht.webp" alt=""><figcaption><p>Übersicht der Theme Konfiguration</p></figcaption></figure>

The theme configuration can be divided into a total of eight sections, which we will discuss in more detail in the following lessons. Each of these eight sections is represented as a tab. These tabs consist of individual configuration fields.

\
Each of these fields has a small blue question mark for help. This help explains the field again briefly and concisely, so that you don't have to refer back to the documentation later if you forget the exact function. Let's start with the configuration! Let's start with the “General” tab.

{% hint style="info" %}
If anything is unclear, please do not hesitate to contact us! We are always interested in improving our documentation. You can find our contact details at the bottom left under the Support tab.
{% 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://docs.atloss.de/en/theme-configuration.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.
