Skip to content

docs: add naming and branding guidance for plugin authors #20

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Quick104 merged 1 commit into from
Sep 6, 2026
Merged

docs: add naming and branding guidance for plugin authors #20

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -248,6 +248,17 @@ Read [CONTRIBUTING.md](CONTRIBUTING.md) and
Public Go, protobuf, runtime, and manifest changes should start as an issue and
identify affected downstream repositories.

## Naming and branding

Give your plugin its own name and mention Silo in the summary, for example
"Trakt sync plugin for Silo". Repository and package names such as
`silo-plugin-trakt` are fine, since "silo" only describes what the code plugs
into. Avoid "Silo[word]" product names such as SiloTrakt, which read as
official, and do not use the Silo logo as your plugin's icon. Set
`publisher_name` to yourself, not "Silo", unless the plugin is published by the
project. The full guidance, including what needs no permission, is at
<https://siloserver.org/brand>.

## License

Apache-2.0. See [LICENSE](LICENSE).
Loading