# Admin Panel's Logo and Branding

This documentation guides you through the easy, precompiled installation of the Admin Panel. Despite the straightforward setup, you can still customize the panel to meet most customer needs.

#### Customizing the Admin Panel

After completing the setup, run `docker volume ls` in the terminal to view all Docker-created volumes. Among these, locate the volume named with `taxiassets`, usually `root_taxiassets`. To obtain detailed information, execute `docker inspect <name>`, replacing `<name>` with the actual volume name. This command will display comprehensive details about the volume.

```scheme
{
    "CreatedAt": "time",
    "Driver": "local",
    "Labels": {
        "com.docker.compose.project": "root",
        "com.docker.compose.volume": "taxiassets"
    },
    "Mountpoint": "/var/lib/docker/volumes/root_taxiassets/_data",
    "Name": "root_taxiassets",
    "Options": null,
    "Scope": "local"
}
```

The `mountpoint` is the directory for storing CMS assets like translation files. Inside, you'll find the `i18n` folder housing translation files that contain CMS branding text. These can be updated to meet specific needs.

```scheme
"branding": {
    "menu": {
        "header": "Ridy"
    },
    "footer": {
        "address": "http://ridy.io/",
        "prefix": "© 2018-2025",
        "title": "Ridy.io",
        "suffix": "All Rights Reserved."
    },
    "page": {
        "title": "Ridy CMS"
    }
}
```

In this folder, you can also find assets such as the logo used in the Admin Panel.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://flutter-docs.taxi.ridy.io/configuration/admin-panels-logo-and-branding.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.