Repository navigation
feat(web): put the logo and the mark on every surface - #14
Merged
Merged
Conversation
`logo.png` and `favicon.png` were committed but never referenced. Wire them into the metadata, the manifest, the pages and the verification mail, behind a shared `components/brand.tsx`. The two assets are not interchangeable. `logo.png` sets "Outreach" in white, so the full wordmark reads on the dark theme and half of it disappears on the light one. `BrandLockup` therefore swaps: the wordmark on dark, the mark from `favicon.png` beside live text on light. Anywhere the background is fixed dark — the closing CTA band — the wordmark is used directly. Anywhere the surface can be either, or the image may not load at all (tab strip, launcher, mail client), it is the mark. Both files were re-encoded first. They carried enough transparent padding that a plain `<img>` reserved four times the box the artwork occupies, and the favicon was a 1.3MB 3:2 PNG — a squashed tab icon fetched on every page load. Trimmed and resized they are 512x512 and 1007x256, at 31KB and 35KB. The artwork is untouched; the originals are in 85faaa7 if the padding turns out to be load-bearing. Plain `<img>`, not `next/image`: the runtime optimiser needs `sharp`, which this workspace does not install, so the standalone image would 500 on the first request for an optimised asset. The service worker pre-caches both with the offline page and moves to v2 — an offline screen that renders a broken image is worse than the browser error it replaces. Co-Authored-By: Claude Opus 5 (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
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.
logo.pngandfavicon.pngwere committed but never referenced. Wire them into the metadata, the manifest, the pages and the verification mail, behind a sharedcomponents/brand.tsx.The two assets are not interchangeable.
logo.pngsets "Outreach" in white, so the full wordmark reads on the dark theme and half of it disappears on the light one.BrandLockuptherefore swaps: the wordmark on dark, the mark fromfavicon.pngbeside live text on light. Anywhere the background is fixed dark — the closing CTA band — the wordmark is used directly. Anywhere the surface can be either, or the image may not load at all (tab strip, launcher, mail client), it is the mark.Both files were re-encoded first. They carried enough transparent padding that a plain
<img>reserved four times the box the artwork occupies, and the favicon was a 1.3MB 3:2 PNG — a squashed tab icon fetched on every page load. Trimmed and resized they are 512x512 and 1007x256, at 31KB and 35KB. The artwork is untouched; the originals are in 85faaa7 if the padding turns out to be load-bearing.Plain
<img>, notnext/image: the runtime optimiser needssharp, which this workspace does not install, so the standalone image would 500 on the first request for an optimised asset.The service worker pre-caches both with the offline page and moves to v2 — an offline screen that renders a broken image is worse than the browser error it replaces.