WIP: Ocotillo rebranding: the favicon - #326
Draft
jirhiker wants to merge 1 commit into
Draft
Conversation
The favicon work rode into staging alongside unrelated changes and was rolled back on fix/revert-ocotillo-favicon. This restores it on a branch that carries nothing else, so the Ocotillo rebranding lands as one reviewable change. Restores the ocotillo mark and its formats -- favicon.svg as the source of truth, favicon.ico with 16/32/48, apple-touch-icon.png at 180x180, and favicon.png as the 48x48 fallback -- with the index.html head links and the FRONTEND.md section documenting how the rasters are regenerated. The mark is painted from palette values only: field brand-950, stems sand-100, blooms bloom-500. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
jirhiker
marked this pull request as draft
August 5, 2026 22:22
jirhiker
changed the title
Preview DeploymentPreview URL: https://preview-feat-ocotillo-favicon-rebrand-auejgdbofq-uc.a.run.app Note: This preview uses the staging API endpoints. |
Contributor
|
👀 OOO, lookin' cool |
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
2 participants
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.
Stacked on fix/revert-ocotillo-favicon — base retargets to
stagingautomatically once that branch merges.Why
The favicon rebrand rode into staging alongside unrelated work. The fix branch rolls it back out of staging; this branch carries the favicon and nothing else, so the Ocotillo rebranding gets reviewed on its own terms.
What's here
The ocotillo mark and the formats browsers actually ask for:
public/favicon.svgpublic/favicon.ico.icopublic/apple-touch-icon.pngpublic/favicon.pngPlus the
index.htmlhead links and the FRONTEND.md section documenting how the rasters are regenerated from the SVG.The mark is painted from palette values only — field
brand-950, stemssand-100, bloomsbloom-500— so it reads as the deep end of the same water-blue ramp that ownsprimary.Not in scope
The
bloom/sandidentity ramps intheme.tsandindex.css, and the brand palette itself, stay in staging. They are palette tokens in their own right and were never reverted.Testing
Assets are byte-identical to what was on staging before the rollback, so this re-lands a state that was already running. Worth a fresh-cache tab check on merge, since browsers cache favicons aggressively.
🤖 Generated with Claude Code