fix(landing): settle the Pharos hero so the ship stays in view#19
Merged
Conversation
The hero plate used background-size: auto 114% anchored to the right, which over-zoomed the engraving: it pushed the ship off the left edge and crowded the lighthouse toward the middle. Switch to a single cover rule biased right of center so the tower sits on the right and the ship returns to view at bottom-left. One crop that reads the same at every width.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Aayam Bansal (aayambansal)
added a commit
that referenced
this pull request
Jul 7, 2026
…k, harden PKCE + push (#122) - refreshAccessToken no longer treats a 429/408 on the token endpoint as a fatal 'sign-in expired'. During a retry storm auth.openai.com rate-limits the token endpoint; the whole 4xx range was fatal, forcing a needless full re-auth. Retry 429/408 (and 5xx) with backoff; only a genuine 4xx reconnects. (#19) - Removed the shared-key quota fallback. On 429/403 it forwarded the ChatGPT-internal Codex model id + Codex-shaped body to api.openai.com (which doesn't know those models → 400s) under process.env.OPENAI_API_KEY, and the substring quota-match could misfire on unrelated 403s → silently charging the user's personal key. Return the 429/403 as-is instead. (#15) - generateRandomString uses rejection sampling for a uniform PKCE verifier (b % 66 biased toward the first 58 chars). (#45) - pushTokensToBackend fetch is bounded by OAUTH_HTTP_TIMEOUT_MS so a hung backend can't leave 'keys signin' spinning after the browser succeeded. (#35)
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.
What
The hero engraving wasn't sitting right: the lighthouse was crowded toward the middle and the ship at the bottom-left was cropped almost entirely off-screen.
Why
The hero plate was sized with
background-size: auto 114%anchored to the right edge. On the wide (2000×1116) engraving that over-zoom pushed the left third — the ship — out of frame and pulled the tower inward.Change
One line of styling on the hero backdrop: switch to a single
background-size: coverwith a right-biasedbackground-position(62% center). The tower now sits on the right where it belongs, and the ship steering by its beam is back in view at the bottom-left. One crop rule, so it reads the same at every width — no separate desktop/mobile behavior to drift.Comment above the plate updated to match. No other files touched.