Repository navigation
feat: update every Sideband logo to the new mark - #27
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Karan4248
added a commit
that referenced
this pull request
Sep 6, 2026
Karan4248
added a commit
that referenced
this pull request
Sep 6, 2026
Karan4248
added a commit
that referenced
this pull request
Sep 6, 2026
Contributor
ScreenshotsAuto-captured from this PR's production build (commit 48bb398).
|
whoisaldo
approved these changes
Sep 6, 2026
This branch was successfully deployed
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.





Closes #25.
What changed and why
The studio mark was redesigned, but the site still shipped the old icon (two squares inside a noisy white ring) as the favicon, social preview, and navbar icon, and every engineer timeline fell back to a plain "S" monogram. This swaps all of them to the new mark.
The source PNGs are opaque with a dark background baked in, so each output is derived rather than dropped in as-is. The mark is a neon glow authored on pure black, which keys out exactly: alpha is the brightest channel, and unpremultiplying the colour rebuilds the glow so it composites over the site's
#06050ethe way it looked on black.Two treatments, for two different jobs:
#000000against the page's#06050eand show the faint edge the issue calls out.app/icon.png) keeps a dark rounded tile. It has to hold up on a light browser tab strip and a white social card, where a bare glow washes out. This also matches the tile in the lettering lockup and the icon it replaces.For the timeline I compared the square mark against the full
sideband.studiolockup in the real 132x40 slot. The lockup renders at roughly 132x21, which puts its text near 7px, right under a 26px "Sideband" heading that already says the name. The square mark renders 40x40 and matches the weight of the Staged and University of Manitoba logos beside it, so that is what shipped.Proof it works
The Sideband row on all three engineer timelines, before and after. Every profile that carries a
company: 'Sideband'entry is here, so the monogram is gone everywhere it appeared:The same change in full page context on
/engineers/karan-anand:Before
After
Navbar at its real 24px and the favicon on a light tab strip and a white card, before and after, with 4x zooms so the change is legible:
What I tested
npm run build,npm run lint,npm run check:consistency,npm run check:copy,npx tsc --noEmitall pass.npx playwright test: 8 passed, including a new smoke test asserting all three Sideband roles render the mark instead of the monogram. Verified it is real coverage by revertinglib/engineers.tsand watching it fail./,/engineers/karan-anand,/engineers/ali-younes, and/engineers/ali-tleison the dev server at 1440px./icon.pngis still a real route in the build output, so theopenGraphandtwitterimage references keep resolving.Note on
prettier --check: it flags 68 files locally, including files this branch never touches. That is this Windows clone checking out withcore.autocrlf=true; with--end-of-line autoeverything passes, and the committed blobs are LF. Nothing to fix here.Out of scope
experiencearray, so there is no fourth timeline to update. The issue's three profiles are all of them.package-lock.jsonstill carries the pre-rebrand nameeternalreverse, so anynpm installdirties the tree. Left alone to keep this PR to one change, worth a separate one-line fix.