System-wide branding: everything says Fedora, nothing says Glarion #5

Open
opened 2026-07-14 19:40:28 +00:00 by james.oates · 0 comments
Owner

Hardware validation of the live ISO (2026-07-14) confirmed the branding gap is total, not cosmetic: boot menu, boot splash, wallpaper, launcher logo, System Settings / Info Center, os-release — all Fedora. The OS image itself carries Fedora identity, so this affects installed systems identically, not just the live ISO.

Scope to audit and rebrand (roughly in user-visibility order):

  • /etc/os-release (NAME, PRETTY_NAME, ID, logo keys — what Info Center and tooling report)
  • Wallpaper (default + lock screen)
  • KDE splash screen and SDDM login theme
  • Plymouth boot splash
  • Launcher/kickoff distro logo and fedora-logos package replacement
  • GRUB menu title on the live ISO (covered by the Titanoboa contract migration, #4 — iso.yaml label)
  • Anaconda installer branding on the unattended ISO (fedora-release/anaconda product strings) — investigate feasibility

Prerequisite: Glarion needs actual brand assets (logo, wallpaper) before most of this can land. Design decision for the user; implementation is then mostly package swaps and file drops in the Containerfile.

Related: #4 (GRUB label), #6 (default app set — the other half of "this doesn't feel like Glarion yet").

Hardware validation of the live ISO (2026-07-14) confirmed the branding gap is total, not cosmetic: boot menu, boot splash, wallpaper, launcher logo, System Settings / Info Center, os-release — all Fedora. The OS image itself carries Fedora identity, so this affects installed systems identically, not just the live ISO. Scope to audit and rebrand (roughly in user-visibility order): - [ ] `/etc/os-release` (NAME, PRETTY_NAME, ID, logo keys — what Info Center and tooling report) - [ ] Wallpaper (default + lock screen) - [ ] KDE splash screen and SDDM login theme - [ ] Plymouth boot splash - [ ] Launcher/kickoff distro logo and `fedora-logos` package replacement - [ ] GRUB menu title on the live ISO (covered by the Titanoboa contract migration, #4 — iso.yaml label) - [ ] Anaconda installer branding on the unattended ISO (fedora-release/anaconda product strings) — investigate feasibility Prerequisite: Glarion needs actual brand assets (logo, wallpaper) before most of this can land. Design decision for the user; implementation is then mostly package swaps and file drops in the Containerfile. Related: #4 (GRUB label), #6 (default app set — the other half of "this doesn't feel like Glarion yet").
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Glarion/glarion#5
No description provided.