> For the complete documentation index, see [llms.txt](https://vitrina-blogerov.gitbook.io/bloggers-showcase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vitrina-blogerov.gitbook.io/bloggers-showcase/product-docs/product-docs-en/showcase-overview/cart.md).

# Cart

The cart collects bloggers that interested the user and turns browsing the catalog into a ready-made request to a manager or agency.

{% hint style="success" %}
The cart is needed for a simple sales flow: the user selects bloggers, clicks the contact button, and receives a prepared inquiry text with a list of the selected cards.
{% endhint %}

### How a blogger gets into the cart

The user can add a blogger:

* from the regular card on the home page;
* from the expanded card;
* after filtering the catalog;
* after AI selection.

After adding, the button on the card changes state. The bottom navigation also shows that the cart already contains selected bloggers.

```mermaid
flowchart TD
    A["User selects a blogger"] --> B["Clicks the add button"]
    B --> C["The card gets cart state"]
    C --> D["Navigation highlights the cart"]
    D --> E["User opens the cart"]
    E --> F["Checks the selection"]
    F --> G["Sends the request"]
```

### What you see in the cart

The cart displays the selected cards and a separate card for returning to the catalog. The user can continue selecting, open a blogger in more detail, or remove extra options.

On the annotated cart screenshot, it is convenient to mark:

* selected cards;
* the delete button;
* the return-to-catalog card;
* the contact button;
* the bottom navigation;
* the visual state of the active cart.

### Removing from the cart

If the user removes a blogger, the card disappears with an animation, and the other elements smoothly rearrange. This preserves the feeling of a neat interface and does not create abrupt jumps on the screen.

If the cart is empty, the request cannot be sent: the showcase indicates that bloggers need to be added first.

<details>

<summary>What is important to show in the demo</summary>

For a video or GIF, three actions work well: add a blogger on the home page, go to the cart, and delete one card. This short scenario shows that the cart works as a full selection list, not just a decorative button.

</details>

### Contact button

In cart mode, the central bottom button turns into a contact button. Its text and link are set in the admin panel.

Usually, the link leads to the Telegram of the manager, agency, or project owner. When clicked, the showcase opens a dialog with a pre-written message.

{% hint style="info" %}
The text of the contact button and the recipient address are configured by the owner in the admin panel. This makes it possible to use the showcase for an agency, a personal manager, a brand, or a separate sales department.
{% endhint %}

### Prepared message

The showcase automatically generates the request text. The message includes a list of the selected bloggers so the user does not have to copy them manually.

Example of the message logic:

```
Hello! I would like to order advertising from you.
These bloggers interested me:

1. Blogger Name
2. Blogger Name
3. Blogger Name
```

The final text depends on the language of the installed version and the content of the cards.

### Connection with the admin panel

The cart uses the data that the owner sets in the admin panel:

* blogger cards;
* blogger names;
* contact button text;
* request link;
* showcase styling;
* the language of the current version.

{% tabs %}
{% tab title="What the owner edits" %}
The owner changes the cards, styling, contact button text, and recipient link through the admin panel.
{% endtab %}

{% tab title="What the user does" %}
The user only selects bloggers and sends a ready-made inquiry. They do not need to manually copy names or make a list.
{% endtab %}
{% endtabs %}

### User flow

The cart covers the showcase's most important path: from interest to action.

1. The user browses the catalog.
2. Adds bloggers of interest.
3. Opens the cart.
4. Checks the selection.
5. Clicks the contact button.
6. Proceeds to the conversation with the manager.

{% hint style="success" %}
For the product owner, the cart is important because it reduces friction before reaching out. The user does not just browse the catalog, but quickly assembles a clear request.
{% 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://vitrina-blogerov.gitbook.io/bloggers-showcase/product-docs/product-docs-en/showcase-overview/cart.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.