> 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/preface.md). # Preface This solution was developed primarily for influencer marketing agencies that need a convenient tool for presenting bloggers and working with potential advertisers. The showcase makes it possible to gather information about bloggers, available ad formats, and cooperation terms in one place. A brand does not have to request statistics, clarify basic details with a manager, or sort through scattered spreadsheets and correspondence — the necessary information is available through the familiar Telegram interface. Unlike a regular website or static catalog, the solution combines a Telegram bot, a mini app, and an admin panel. Agency staff can update data on their own, manage the showcase content, and adapt it to their own brand without making changes to the code. Special attention has been paid to localization. The system supports independent language versions with separate content and management, so the showcase can be used simultaneously in multiple markets without being limited to a simple machine translation of the same catalog. The documentation describes installation, initial setup, the system structure, and day-to-day work with the admin panel. It is intended both for technical specialists carrying out the deployment and for agency employees who will manage the showcase after launch. --- # 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/preface.md?ask=&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.