简体中文
EnglishWhat Is theme.park?
Updated
theme.park is an open-source collection of themes and skins for self-hosted applications. According to the project's site, it covers 48 themed applications, with CSS addons available on certain themes. It is aimed at people running their own apps—typically in Docker or behind a reverse proxy—who want a consistent look across their services. The project provides documentation, a GitHub repository, and a Discord community for support.
What the project provides
The core offering is a set of CSS-based themes that restyle the web interfaces of supported apps. Beyond the base themes, some themes include CSS addons that extend or adjust the styling. The project also publishes a Docker image for self-hosting the CSS files, so you can serve the theme assets from your own infrastructure rather than relying on an external source.
Supported installation methods
The site lists several ways to apply the themes, which matters because the right method depends on how your apps are deployed:
| Method | Applies to |
|---|---|
| Custom Docker mods | linuxserver.io containers |
| Custom scripts | Select Hotio containers |
| Subfiltering examples | Web servers such as Nginx, Apache, Caddy, and Traefik |
| Self-hosted CSS | Docker image for serving the CSS files yourself |
If your apps run as linuxserver.io containers, the Docker mod route is the most direct. If you use Hotio containers, check whether a custom script exists for your app. If you prefer to inject the theme at the web server layer, the subfiltering examples for Nginx, Apache, Caddy, and Traefik show how to do it.
How to get started
- Check the documentation. The site directs users to its documentation page for information on each individual theme. Confirm your app is among the 48 supported applications and note whether the theme has addons.
- Pick an installation method based on your setup, using the table above. For linuxserver.io containers, use the Docker mod; for Hotio, look for a custom script; for reverse-proxy setups, follow the subfiltering example for your web server.
- Apply the theme and verify. After installation, reload the app's web interface and confirm the styling has changed. If it hasn't, the most common causes are a mismatched container type, a proxy configuration that isn't passing the CSS through, or a theme that doesn't cover the specific app version you run.
- Get help if needed. The project points users to GitHub for theme issues and to its Discord server for live support.
Community themes and contributing
Beyond the official themes, the project maintains a separate page for community themes. If you have a color scheme you'd like to see added, the project invites you to submit a pull request on GitHub. The project describes itself as open source and made with love, with links to sponsor it or star and fork the repository.
When theme.park is a good fit
theme.park suits self-hosters who run multiple apps and want a unified visual style without restyling each app by hand. It is less useful if your apps aren't among the supported 48, if you don't control the deployment layer (Docker, Hotio, or a reverse proxy), or if you need a guarantee of ongoing maintenance—as a community-driven open-source project, support runs through GitHub and Discord rather than a commercial agreement.