fix(frontend): match website favicon.svg artwork to the rest of the icon set - #5743
Conversation
The tab icon on agenta.ai did not match the docs (and every other Agenta surface). Browsers prefer the SVG favicon over the .ico when both are declared, so favicon.svg — not favicon.ico — is what actually renders, and it was the only asset in the set drawn from different measurements. The two .ico files are byte-identical; favicon.svg was hand-authored separately in the on-page-SEO commit and its transform was eyeballed: the symbol came out at 53.1% x 43.8% of the tile against ~71.5% x 58.6% everywhere else, on a #0A0A0B tile instead of #1E1C1D. Rescale the symbol to scale(2.14) at translate(73 105) and correct the tile fill and radius, which reproduces the bounding box of android-chrome-512x512.png to within a pixel: favicon.svg x[73..437] y[105..403] canonical x[73..438] y[106..404] Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
dosubot
Bot
added
size:XS
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Website previewPreview URL: https://pr-5743-agenta-website-preview.mahmoud-637.workers.dev Built from |
|
I told it not to open a PR until I test it 🤣 |
|
Looks good to me |
2 participants
Problem
The tab icon on the marketing site doesn't match the docs — the mark sits noticeably smaller inside its tile:
#0A0A0Bbackground#1E1C1DbackgroundCause
Not the
.ico—website/public/favicon.icoanddocs/static/images/favicon.icoare byte-identical (5e12f86a85e98a99634fa48bdc06b291).The site declares four icons and lists the SVG first:
Every modern browser prefers an SVG favicon when one is offered, so
favicon.svgis what actually renders — the.icois never reached. Docs declare only the.ico(docusaurus.config.ts), which is why they look right.favicon.svgturned out to be the one asset in the set that wasn't generated from the brand source. It was hand-authored in eb3d176 (on-page SEO) and itstransformwas eyeballed. Measured mark bounding boxes across the set:favicon.ico(= docs)#1E1C1Dfavicon-32x32.png,favicon.png#1E1C1Dfavicon-16x16.png#1E1C1Dapple-touch-icon.png#1E1C1Dandroid-chrome-192/512.png#1E1C1Dfavicon.svg#0A0A0BFix
Rescale the symbol and correct the tile fill and corner radius in
website/public/favicon.svg. One file, two lines — no other asset needed changing.Verified by rendering the SVG at 512px and comparing the mark's bounding box against
android-chrome-512x512.png:Preview
Both docs and website
