themepark-dev/theme.park

A collection of themes/skins for 50 selfhosted apps!

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 22nd, 2026
Created on August 13th, 2018
Open Issues & Pull Requests: 30 (+0)
GitHub issues: Enabled
Number of forks: 835
Total Stargazers: 3,091 (+0)
Total Subscribers: 30 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 22.3 days
Mean response time: 111.5 days
90th percentile: 429.1 days
Tracked items: 33

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 272 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (22)
  • spam (2)
  • help wanted (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Theme.park is a CSS theming collection that provides customizable skins for self-hosted applications.

The project solves the problem of inconsistent or unappealing user interfaces across multiple self-hosted services by offering a centralized library of themes that can be applied to dozens of applications. It works by providing CSS stylesheets that override default application styling, with support for deployment via Docker and integration methods like nginx subfilter and docker-mods. Users can select from multiple named themes and apply them to their applications through configuration.

Theme.park suits anyone running multiple self-hosted applications who wants visual consistency and the ability to switch between different color schemes across their entire stack. It works well for users comfortable with CSS-based customization and those running containerized deployments. The project supports community-contributed themes and allows users to create custom themes by extending the existing framework.

The project maintains active development with regular theme additions and refinements to existing skins. Community contributions are actively integrated into the codebase. Documentation is comprehensive and kept current alongside feature development. The maintainers respond to user feedback and incorporate requests for new application support and theme variations.