mirror of
https://codeberg.org/forgejo/docs.git
synced 2024-11-24 18:09:26 -05:00
d12a9fee60
Preview: https://forgejo.codeberg.page/@docs_pull_427/docs/next/admin/customization/ --- The previous version of this document insinuated that you need to be familiar with Forgejo's source code and compile Forgejo from source for custom branding changes. As of the most recent Forgejo version, this is not necessarily true, as custom files can be served from the CustomPath. Administrators that were not developers therefore dismissed the other guide and its contents without reading this, and I was one of them. I thought it would make sense for this file to provide information on where to put a custom logo. This change does not fix it (this will be done later), but it will reduce the confusion for now. This warning confused me personally and other Forgejo users, as I had one person tell me IRL that they thought that it was not possible to serve a custom logo. Reviewed-on: https://codeberg.org/forgejo/docs/pulls/427 Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org> Co-authored-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net> Co-committed-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net> |
||
|---|---|---|
| .. | ||
| actions.md | ||
| adopt.md | ||
| command-line.md | ||
| config-cheat-sheet.md | ||
| customization.md | ||
| database-preparation.md | ||
| email-setup.md | ||
| incoming-email.md | ||
| index.md | ||
| installation-binary.md | ||
| installation-docker.md | ||
| installation.md | ||
| LICENSE | ||
| logging-documentation.md | ||
| moderation.md | ||
| oauth2-provider.md | ||
| recommendations.md | ||
| reverse-proxy.md | ||
| search-engines-indexation.md | ||
| seek-assistance.md | ||
| signing.md | ||
| storage.md | ||
| upgrade.md | ||