> 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/theme-konfiguration/allgemein/status-ausgaben.md).

# Status-Ausgaben

### Übersicht

Die Status-Ausgaben treten bei Interaktion mit dem Online Shop an unterschiedlichen stellen auf. Im Allgemeinen sind dies Meldungen, welche den Besucher über verschiedene Ereignisse in deinem Shopware Shop informieren. Im folgenden siehst du ein paar Beispiele:

<div align="center"><figure><img src="https://3272904207-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpapLvT9HTe34BQRCbfyY%2Fuploads%2FV5GAeb7KxoiDjoZAcJBR%2Fstatus-success.webp?alt=media&amp;token=8df77ac4-8bbe-43d4-a034-24a7027ea0f5" alt="" width="375"><figcaption><p>Erfolgreiche Status-Ausgabe</p></figcaption></figure> <figure><img src="https://3272904207-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpapLvT9HTe34BQRCbfyY%2Fuploads%2FfeD3O7wNqcsDTaybOZwS%2Fstatus-info.webp?alt=media&amp;token=736c4b02-411e-465a-a56b-bd4e92528b22" alt="" width="375"><figcaption><p>Informative Status-Ausgabe</p></figcaption></figure></div>

<div><figure><img src="https://3272904207-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpapLvT9HTe34BQRCbfyY%2Fuploads%2F2NT2nLmbx5zQix5ctNSb%2Fstatus-warning.webp?alt=media&amp;token=7bad21ce-2d43-4957-8319-612fc1731bd4" alt="" width="372"><figcaption><p>Warnende Status-Ausgabe</p></figcaption></figure> <figure><img src="https://3272904207-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpapLvT9HTe34BQRCbfyY%2Fuploads%2FxLIJDP8edLrFwgUPLOni%2Fstatus-danger.webp?alt=media&amp;token=be2196d4-e5f3-4df1-bb99-ef2cb4c0a542" alt="" width="373"><figcaption><p>Fehlerhafte Status-Ausgabe</p></figcaption></figure></div>

### Konfiguration

<figure><img src="https://3272904207-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpapLvT9HTe34BQRCbfyY%2Fuploads%2FoEfBstPl18QcUsMtoAXN%2Fstatus-ausgaben.webp?alt=media&amp;token=d93ea969-58a5-488c-9832-d1ac363bab00" alt=""><figcaption></figcaption></figure>

<details>

<summary>Erfolg</summary>

Die Farbe für erfolgreiche Status-Ausgaben.

***

[Variable:](/academy/fachbegriffe/variable.md) `$sw-color-success`

</details>

<details>

<summary>Information</summary>

Die Farbe für informative Status-Ausgaben.

***

[Variable:](/academy/fachbegriffe/variable.md) `$sw-color-info`

</details>

<details>

<summary>Hinweis</summary>

Die Farbe für warnende Status-Ausgaben.

***

[Variable:](/academy/fachbegriffe/variable.md) `$sw-color-warning`

</details>

<details>

<summary>Fehler</summary>

Die Farbe für fehlerhafte Status-Ausgaben.

***

[Variable:](/academy/fachbegriffe/variable.md) `$sw-color-danger`

</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://docs.atloss.de/theme-konfiguration/allgemein/status-ausgaben.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.