Can I contribute my own color scheme to theme.park?

Updated

Yes. theme.park is an open-source, community-driven project, and the site explicitly invites users to contribute color schemes: if you have a good color scheme you'd like to see added, you can PR it (submit a pull request) on GitHub. The site also separates "Official theme options" from "Community Themes," so contributions can live alongside the official set rather than replacing it.

What the site says about contributing

The theme.park homepage makes the contribution path clear in a few places:

  • Community Themes section: The site links out to community themes, showing that user-made themes are a recognized part of the project.
  • "Got a good color scheme you'd like to see added? PR it!" This is the direct invitation to submit your work via GitHub.
  • Open-source framing: The footer notes the project is open source ("Is it really open source if it's not made with love?"), reinforcing that outside contributions are expected.

How the contribution process works

The site does not publish a detailed contribution guide on the homepage, so the practical steps follow standard GitHub open-source practice:

  1. Fork the repository on GitHub (the site links to its GitHub page from the homepage).
  2. Add your theme or color scheme following the structure of existing themes. The documentation page is the reference for how each theme is organized.
  3. Open a pull request describing the color scheme and which app(s) it targets.
  4. Respond to review feedback — maintainers and the community may ask for adjustments before merging.

What to check before submitting

  • Match the existing format. Since themes are applied as CSS (via Docker mods, scripts, or webserver subfiltering), your contribution should follow the same file and naming conventions as current themes.
  • Target a supported app. The project covers 48 themed applications; a scheme for an app outside that set may need more discussion.
  • Test it in a real deployment. The documented installation methods — custom Docker mods for linuxserver.io containers, custom scripts for select Hotio containers, and subfiltering through Nginx, Apache, Caddy, or Traefik — are the environments where your CSS will actually run.

Where to get help with a contribution

  • GitHub: The site directs users with theme issues to GitHub, which is also where pull requests and review discussion happen.
  • Discord: The project runs a Discord community for live support, useful if you're unsure whether a scheme fits the project's direction.
  • Documentation: The theme docs page explains each theme in detail and is the best starting point for matching existing conventions.

Practical expectations

Contributing a color scheme is a code contribution, not a request form — you'll be working in the project's repository and CSS structure. The site's own wording ("PR it!") sets that expectation directly. If you only have a color idea without the CSS work, the Discord community is the better place to gauge interest first.