Favicon: regenerate from logo so they match#60
Merged
Conversation
The favicon was the original v2.6.1 orange cartoon-fox silhouette; the panel logo (sidebar, login page) is the green geometric circuit- kitsune in a ring. Two completely different aesthetics — looking at the browser tab next to the panel, they didn't read as the same brand. Regenerated favicon.svg / favicon-16x16.png / favicon-32x32.png / favicon.ico from frontend/public/kitsune-command-logo-transparent.png so all four favicon variants are direct downsamples of the canonical logo source. The SVG embeds a 96px raster of the same source instead of being hand-drawn. Reasoning: redrawing the logo as a clean vector path would diverge from the source over time, and the logo's circuit traces don't survive a faithful path-only redraw at 16-32px anyway. Pinning the SVG to the same raster source means every favicon variant stays in lockstep with the logo — change the logo, run the script, all four files update together. Tradeoff at 16px: the fine circuit-trace line art washes out into a soft green silhouette. Modern browsers prefer the SVG path (which scales fluidly to whatever DPI the tab renders at), so the 16px raster is mostly a historical fallback. Could tune a bolder 16px variant later if the tab strip looks too washed out. Tooling: tools/regen-favicons.py is the regen script. Pillow only, no extra deps. Source path + output paths hardcoded so it just works from repo root. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The browser-tab favicon was the original orange cartoon-fox silhouette from v2.6.1. The actual panel logo (sidebar, login) is the green geometric circuit-kitsune in a ring. Side-by-side they didn't read as the same brand.
This PR regenerates all four favicon variants (`favicon.svg`, `favicon-16x16.png`, `favicon-32x32.png`, `favicon.ico`) from `frontend/public/kitsune-command-logo-transparent.png` so they're direct downsamples of the canonical logo. Browser tab now matches the panel.
Approach
The SVG embeds a 96px raster of the logo (base64) rather than being a hand-drawn path. Why:
Tradeoff at 16px
The fine line-art washes out at 16×16 into a soft green silhouette in a circle. Modern browsers prefer the SVG (which scales fluidly to whatever DPI the tab renders at), so the 16px raster is mostly a historical fallback. If the tab strip looks too washed out we could hand-tune a bolder 16px variant later — but that'd diverge from the source-of-truth logo, which is the whole thing this PR fixes.
Files
Test plan
🤖 Generated with Claude Code