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

# Welcome

You have chosen one of our extensions - congratulations! We look forward to welcoming you as part of the community.

### Theme users

Our themes are all based on the same configuration basis and are characterized by continuous further development, a variety of [configuration options](https://docs.atloss.de/en/theme-configuration.md) and [features](https://docs.atloss.de/en/included-extensions/features.md) already included, as well as excellent expandability with third-party apps.

Do many stores look the same to you? Not with us! With our theme, you can experience e-commerce at the highest level thanks to a modern and, above all, sophisticated design.

Let's start straight away with the setup! However, please note that technical terms will crop up throughout the documentation. So that you can make the best use of the documentation, we recommend that you familiarize yourself with the necessary technical terms via our [Academy](https://docs.atloss.de/en/academy/technical-terms.md). These are linked at every point in the documentation. This will enable you to make optimum use of the theme configuration and understand the effects on your online store even better.

### App users

Let's not beat about the bush and get straight to setting up! You can select the relevant app on the left-hand side to find out more information about the setup.


---

# 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/welcome.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.
