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

# Profile

The profile shows the user that the showcase is open inside a Telegram Mini App and displays the current Telegram account data if Telegram has passed it to the app.

{% hint style="info" %}
The profile is not a personal account in the classic sense. It is a lightweight identity and navigation screen within the showcase.
{% endhint %}

### When the profile is useful

The profile helps the user understand that they are in a Telegram app, not on a regular external page. This is especially important when the showcase is opened via a bot button.

On the annotated profile screenshot, it is useful to mark:

* user avatar;
* user name;
* username;
* an informational message about the data;
* the developer's button or link;
* the bottom navigation;
* guest state, if Telegram data is unavailable.

### Telegram data

If the showcase is open inside Telegram, the profile can show:

* avatar;
* name;
* last name;
* username.

This data comes from Telegram Web App and is used only for display on the profile screen.

```mermaid
flowchart TD
    A["Telegram Mini App"] --> B["Passes user data"]
    B --> C["The showcase displays the profile"]
    C --> D["Avatar"]
    C --> E["Name"]
    C --> F["Username"]
```

{% hint style="success" %}
The profile explicitly states that the app does not collect or store the user's personal data. This reduces anxiety and makes the interface clearer.
{% endhint %}

### Guest state

If Telegram did not pass user data or the showcase is open in a regular browser, the profile shows a guest state.

In this case, the user can still browse the catalog, use search, filters, and the cart. Only a neutral guest profile will be shown instead of the Telegram name.

{% tabs %}
{% tab title="In Telegram" %}
The profile shows the Telegram account data: avatar, name, and username, if they are available to the app.
{% endtab %}

{% tab title="In the browser" %}
The profile works as a guest screen. The main showcase features remain available.
{% endtab %}
{% endtabs %}

### Navigation

Switching to the profile is done through the bottom navigation. When the profile is opened, the showcase hides the catalog or cart mode and shows a separate screen.

When returning to the home screen, the user sees the catalog again. If a result set had previously been formed or bloggers selected, the interface preserves the working state within the current session.

<details>

<summary>What happens when switching sections</summary>

When moving between the home screen, cart, and profile, the active interface mode changes. The showcase does not open a new page, but smoothly switches the state of the current screen. Therefore, transitions look faster and softer than a regular website reload.

</details>

### Profile animation

Profile data appears with a typing effect. This supports the overall character of the showcase: the interface looks lively, light, and premium.

For a demo, you can record a short clip: open the bottom navigation, go to the profile, and wait for the name and informational message to appear.

### Language and version

The profile is displayed in the language of the installed version of the showcase. If the client has the Russian version installed, the profile will be in Russian; if the English, Chinese, or Arabic version is installed, it will be in the language of the corresponding version.

{% hint style="warning" %}
The profile does not switch the language of the entire platform. The language is determined by the installed language version of the project.
{% endhint %}

### What to explain to the client

The profile is needed not for complex authorization, but for trust and context. The user sees that the Mini App understands the Telegram environment, but does not require registration or force them to fill out unnecessary forms.


---

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