> 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/architecture/language-versions.md).

# Language versions

A language version is a separate operating environment for a specific market. It includes its own storefront, backend, Telegram bot, PostgreSQL, settings, content, administrators, and public address.

{% hint style="success" %}
Localization in the platform is not just interface translation. It is the ability to maintain independent catalogs for different markets, brands, bloggers, prices, and communications.
{% endhint %}

### Supported versions

| Code | Language |
| ---- | -------- |
| `ru` | Russian  |
| `en` | English  |
| `zh` | Chinese  |
| `ar` | Arabic   |

Each version is delivered as a separate archive:

```
bloggers_bot_ru.tar.gz
bloggers_bot_en.tar.gz
bloggers_bot_zh.tar.gz
bloggers_bot_ar.tar.gz
```

### What is included in one version

<details>

<summary>Contents of a language version</summary>

Inside one version there is a FastAPI backend, a Telegram bot, PostgreSQL, an assets folder, a file `.env`, an admin panel, content database, AI settings, and Telegram settings.

</details>

<details>

<summary>What is specific to each version</summary>

Each version has its own cards, tags, prices, texts, media, Telegram bot token, bot users, AI API key, prompts, channel ID, and administrators.

</details>

<details>

<summary>What is shared</summary>

Shared elements are edge-Caddy, the domain, server infrastructure, and platform management utilities.

</details>

### Addresses

{% tabs %}
{% tab title="RU" %}

```
https://example.com/bloggers/ru/
```

{% endtab %}

{% tab title="EN" %}

```
https://example.com/bloggers/en/
```

{% endtab %}

{% tab title="ZH" %}

```
https://example.com/bloggers/zh/
```

{% endtab %}

{% tab title="AR" %}

```
https://example.com/bloggers/ar/
```

{% endtab %}
{% endtabs %}

### How the language is chosen

```mermaid
flowchart TB
    A["User opens the domain"] --> B{"Is there a Telegram language?"}
    B -->|yes| C["Check the installed version"]
    B -->|no| D["Check browser language"]
    C --> E{"Is the version installed?"}
    D --> E
    E -->|yes| F["Open /bloggers/{lang}/"]
    E -->|no| G["Fallback: en -> zh -> ar -> ru"]
```

### Working with multiple markets

{% hint style="info" %}
The same server can serve different markets. For example, the Russian version can work with local brands, while the English version can work with international bloggers and a separate Telegram bot.
{% endhint %}

At the same time, the versions do not interfere with each other: content is transferred only through a special utility, and secrets and users are not copied.

### Important

{% hint style="warning" %}
Do not use one Telegram bot token in multiple language versions. This will lead to conflicts in polling, the mini app button, and the bot's audience.
{% endhint %}

If you need the same design in all versions, it must be configured in each version or transferred through the content management utility.


---

# 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/architecture/language-versions.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.