One of Strapi's main feature is its fully extendable and customizable admin panel. This section explains how the admin panel section is structured and how to customize it.
See the [Contributing Guide](https://github.com/strapi/strapi/blob/master/.github/CONTRIBUTING.md) for informations on how to develop the Strapi's admin interface.
## Files structure
The entire logic of the admin panel is located in a single folder named `./admin/`. This directory contains the following structure:
The administration panel can be customised according to your needs, so you can make it reflects your identity: colors, fonts, logo, etc.
### Change access URL
By default, the administration panel is exposed via [http://localhost:1337/admin](http://localhost:1337/admin). However, for security reasons, you can easily update this path.
Admin's styles use [PostCSS](https://github.com/postcss/postcss), and more precisely [PostCSS-SCSS](https://github.com/postcss/postcss-scss). In this way, colors are stored in variables. The values of these variables can be easily changed in files located in `./admin/admin/src/styles/variables/`.
This will replace the folder's content located at `./admin/admin/build`. Visit http://localhost:1337/admin/ to make sure your updates have been taken in account.
***
## Deployment
There is three cases to deploy the administration panel:
1. On the same server as the API.
2. Without the plugins on another server (AWS S3, Azure, etc) as the API.
3. With the plugins on different servers as the API.
Let's dive into the build configurations. The file should look like this:
**Path —** `./config/environment/**/server.json`.
```json
{
"admin": {
"build": {
"host": "https://admin.myapp.com",
"backend": "https://api.myapp.com:8080",
"plugins": {
"source": "host",
"folder": "/plugins"
}
}
}
}
```
#### On the same server as the API
You don't need to touch anything in your configuration file. This is the default behaviour and the build configurations will be automatically set.
#### Without the plugins on another server
**Path —** `./config/environment/**/server.json`.
```json
{
"admin": {
"build": {
"host": "https://admin.myapp.com",
"backend": "https://api.myapp.com:8080",
"plugins": {
"source": "origin"
}
}
}
}
```
The administration URL will be https://admin.myapp.com and every request from the panel will hit the backend at https://api.myapp.com:8080. The plugins will be injected through the `origin` (means the API itself). In other words, the plugins URLs will be `https://api.myapp.com:8080/admin/content-manager/main.js`.
> Note: The plugins are injected using the `./admin/admin/build/config/plugins.json`. To see the plugins URLs in the `index.html`, you need to launch the administration panel in the browser.
#### With the plugins on another server
In this case, we suppose that you decided to put your administration and the plugins on the same server but on a different server as the API.
**Path —** `./config/environment/**/server.json`.
```json
{
"admin": {
"build": {
"host": "https://admin.myapp.com",
"backend": "https://api.myapp.com:8080",
"plugins": {
"source": "host",
"folder": "plugins"
}
}
}
}
```
The administration URL will be https://admin.myapp.com and every request from the panel will hit the backend at https://api.myapp.com:8080. The plugins will be injected through the `host`. It means that the plugins URLs will use the host URL as the origin. So the plugins URLs will be `https://admin.myapp.com/plugins/content-manager/main.js`.
We also added a `folder` setting to separate the plugins from the administration build. In your server, the files structure should look like this:
> Note: The plugins are injected using the `./admin/admin/build/config/plugins.json`. To see the plugins URLs in the `index.html`, you need to launch the administration panel in the browser.