Themes in every app

What it is

When you pick a theme, WolOS writes matching styles for every toolkit on the system: GTK 3 and 4, Qt, Helium and Firefox, the foot terminal, the code editor and the zsh prompt.

Why

A theme that stops at the desktop's own apps makes every other window look out of place. Generating each toolkit's style from the same colour tokens keeps them in step, and tests check every text colour for contrast.

How

1. Pick a theme: Settings > Appearance, the theme picker (Ctrl+Super+T), or wol theme set <id> (wol theme list shows the ids). You see the shell, window borders, the lock screen, the terminal and the prompt change together.
2. Restart apps that did not change. Most apps switch live; some pick it up when they restart, as the table below says.
3. Make your own: Settings > Appearance > Make a theme (Theme Studio), or wol-hue from a picture.

If something goes wrong

Related

wol-hue · Plugin Maker and Theme Studio · Settings

Reference

Decision record: ADR 0031 (themes and layouts, themes v2), ADR 0032 (Console).

Source: crates/core/src/theme/{apps,generate,hypr,terminal,console,templates,packs,scaffold,firefox,sourceview,helium,kvantum}.rs. One palette, every consumer: generate::consumers is the full list of files a switch writes. Files go to $XDG_CONFIG_HOME/wolos/toolkits/ and are linked into $XDG_CONFIG_HOME / $XDG_DATA_HOME (a real user file is never replaced). The image ships the wol-light render under /usr/share/wolos (toolkit files) and /usr/share/wolos/toolkits (console files but starship, whose default is the shipped starship.toml); WOL_REGEN=1 cargo test -p core rewrites both.

Terminal palette (terminal::palette): a theme may list its own 16 colours ("terminal": [...] in theme.json, inherited through extends); otherwise red, green, yellow and magenta are the danger, success, warning and accent tokens and the rest a fixed set per variant. Prompt roles (console::roles: accent, muted, ok, error, suggest, warn) read >= 4.5:1 on the terminal background (suggest >= 3:1), the same in every shell.

Catalogue: built-ins, /usr/share/wolos/themes, $XDG_CONFIG_HOME/wolos/themes and the [[theme]] files of enabled plugins (packs, ThemeCatalog::installed; a pack never replaces a known id). Settings > Appearance (crates/shell/src/ui/settings/appearance.rs): Light / Dark / Auto, accent, the theme gallery, a "From Plugins" row, the wallpaper and "Theme from your wallpaper" (generate::from_samples, saved as the user theme from-wallpaper, always passes check()). The picker panel (ui/theme_picker.rs) shows the same gallery.

Rules (tests): scaffold metrics (shared::theme::scaffold) equal the Kit's kit.css and hyprland.conf; window buttons sit on the right, close rightmost, then zoom and minimise (GTK gtk-decoration-layout / gsettings button-layout :minimize,maximize,close, Firefox, the About panel and the compositor title bar alike), 12 px, 22 px apart, the close centre 23 px in from the window's right edge in GTK 3, GTK 4, Firefox and the compositor title bar; they are WolOS's own: one quiet circle (the text colour half way over the surface), the symbolic close, minimise and zoom glyphs while the pointer is over the group, and the accent (a shade deeper pressed) on the button under the pointer, never red, amber and green (apps::tests::window_controls_are_wolos_own; the compositor title bar shows the neutral circle and the ink glyph and takes the accent on hover and press, crates/realtime/tests/hypr_conf.rs); every accent is a token or a documented mix of tokens (accent::tests::accents_come_from_the_tokens) and the default themes are made of the design tokens (theme::tests::default_themes_are_made_of_the_design_tokens); every theme's GTK 3 and GTK 4 sheets parse in the real toolkit (tests/toolkit_css.rs); every console file parses as its format (TOML, KDL, JSON, ghostty lines) for every theme (console::tests); the shipped hyprland.conf has no colour literal but the start-up black (hypr::tests); per-app touch-ups key on the app's own classes (Files views, Calculator keys); no stock Adwaita blue survives; GTK 3 CSS has no GTK 4-only syntax; GTK 3 window buttons are drawn on the titlebutton (Chromium renders no image background under GTK 3); every text colour derived from a token reads >= 4.5:1 on its background; the settings portal backend is gtk (reads the gsettings wol theme sets).