2020-05-01 21:22:26 +00:00
# Customizing Soapbox
2022-07-18 17:12:50 +00:00
Soapbox uses your own site's name and branding throughout the interface.
This allows every Soapbox site to be different, and catered to a particular audience.
Unlike Mastodon, which uses the "Mastodon" branding on all instances, Soapbox does not refer to itself in the user interface.
2020-06-27 17:19:39 +00:00
2022-07-18 17:12:50 +00:00
## Backend settings
2020-05-01 21:44:28 +00:00
2022-07-18 17:12:50 +00:00
The site's name and description are **configured in the backend itself.**
These are settings global to your website, and will also affect mobile apps and other frontends accessing your website.
2020-05-01 21:44:28 +00:00
2022-07-18 17:12:50 +00:00
- On Mastodon, you can change it through the admin interface.
- On Pleroma, it can be edited through AdminFE, or by editing `config/prod.secret.exs` on the server.
2020-05-14 15:28:04 +00:00
2022-07-18 17:12:50 +00:00
These settings are exposed through the API under GET `/api/v1/instance` .
2020-05-14 15:28:04 +00:00
2022-07-18 17:12:50 +00:00
## Soapbox settings
2020-05-01 21:44:28 +00:00
2022-07-18 17:12:50 +00:00
Most settings are specific to your Soapbox installation and not the entire website.
That includes the logo, default theme, and more.
2020-05-01 21:44:28 +00:00
2022-07-18 17:12:50 +00:00
- On Pleroma, admins can edit these settings directly from Soapbox. Just click "Soapbox config" in the sidebar, or navigate directly to `/soapbox/config` .
- On Mastodon, admins need to upload a JSON file with the settings, and make it available at `https://yoursite.tld/instance/soapbox.json` .
2020-06-12 21:31:38 +00:00
2022-07-18 17:12:50 +00:00
If using Pleroma, these settings are exposed through the API under GET `/api/pleroma/frontend_configurations` .
Otherwise, the settings need to be uploaded manually and made available at GET `/instance/soapbox.json` .