Description
Currently, the selected theme is persisted in the browser's localStorage, which means every new browser or device starts with the default Proxmox UI until the user manually selects a ProxMorph theme.
It would be great to have a way to define a server-side default theme, so that any user accessing the Proxmox interface for the first time (or from a new browser) automatically gets a predefined ProxMorph theme instead of the stock UI.
Use case
For homelab or team setups where the admin wants a consistent look across all clients without requiring each user to manually select a theme.
Suggested approach
A fallback value could be injected into the HTML template (e.g. index.html.tpl) so that when localStorage has no proxmorph-theme key set, the script falls back to a configurable default theme instead of no theme at all.
Something like:
var currentTheme = localStorage.getItem('proxmorph-theme') || 'theme-default.css';This default could be configurable via the install script.
Description
Currently, the selected theme is persisted in the browser's
localStorage, which means every new browser or device starts with the default Proxmox UI until the user manually selects a ProxMorph theme.It would be great to have a way to define a server-side default theme, so that any user accessing the Proxmox interface for the first time (or from a new browser) automatically gets a predefined ProxMorph theme instead of the stock UI.
Use case
For homelab or team setups where the admin wants a consistent look across all clients without requiring each user to manually select a theme.
Suggested approach
A fallback value could be injected into the HTML template (e.g.
index.html.tpl) so that whenlocalStoragehas noproxmorph-themekey set, the script falls back to a configurable default theme instead of no theme at all.Something like:
This default could be configurable via the install script.