How ozkansoyturk/jellyfintheme works
Project Type and Purpose
• This is an open-source theming tool / plugin for the Jellyfin web interface.
• Its sole purpose is to provide a “glassmorphism” look via a single CSS file plus static assets (images).
Main Components
a. Jellyfin Media Server
• The core server application that serves the web UI.
b. User’s Web Browser
• Client that requests the Jellyfin UI and applies the custom CSS.
c. Theme Repository (GitHub)
• Source of truth for theme.css and the assets/ folder.
d. CDN (jsDelivr)
• Hosts the raw CSS so users can link via @import quickly.
e. Static Assets Store
• Could be GitHub itself (via raw URLs) or a separate static-file host.
Relationships and Data Flows
• The browser loads the Jellyfin Web UI from the Jellyfin Media Server.
• As part of the UI, the user has configured a custom CSS import that points to the CDN URL.
• The browser fetches theme.css from jsDelivr.
• CSS rules reference images and other assets under assets/, which the browser fetches from GitHub or CDN.
• The browser renders the modified UI with “glassmorphism” effects.
Architectural Patterns and Principles
• Separation of concerns:
• Core application (Jellyfin) vs. theming (CSS & static assets).
• Externalizing the theme on a CDN ensures minimal impact on server performance.
• CDN caching to optimize delivery of static resources.
• GitHub as the single source of truth for code and versioning.