Repository navigation
site: show who is signed in, or Sign in, in the header (FW-601) - #44
Merged
Merged
Conversation
The header on the landing page and /pricing gets an account slot beside the GitHub button: - Signed out, it reads Sign in, linking to /login. - Signed in, it shows the account's initial and address. A menu says who is signed in and offers Account, Console and Sign out. An account still on the waitlist gets Waitlist instead of Console. Signing out stays on the page and puts focus on Sign in; a sign-out that fails says so in the menu. - The landing page is prerendered with no session, so the slot keeps one width and shows nothing until the service answers. Someone signed in never sees Sign in flash by, and the links never move. If the service can't be asked, it offers Sign in. Below 1100px the slot narrows to the initial and the GitHub button to its mark, so the links fit as before. Below 851px the menu hangs from the header's right edge so it stays inside the window. The "How it works" menu's close-on-outside-press, Escape and tab-out handling moves into a useDismiss hook that both menus use, and its panel motion into lib/panel.ts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 13, 2026
Contributor
|
Landed on preview through #47, which merged this branch together with the other two FW-60x PRs on top of the Paygate billing work. Your commits are unchanged. Changes made during the merge: the profile-name migration is renumbered to |
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.
What this does
FW-601: sign-in state in the header. The header on the landing page and
/pricinggets an account slot beside the GitHub button, so visitors can sign in from there and people who are signed in can see that they are./login.Refactor: the "How it works" menu's dismissal (outside press, Escape, tabbing out) moves into a
useDismisshook that both menus use. Its panel animation moves tolib/panel.ts. Its behaviour is unchanged, and the tests cover it.No service changes: this works with the Worker as it is deployed now.
Testing
npm --prefix site run checkpasses, anddocs/matches a rebuild./pricingbehaves the same.Merging with the other two PRs
The profile-name PR (FW-602) builds on this one: merge this first. This PR, FW-602 and #43 (FW-603, open sign-up) each rebuild
docs/, so whichever merges second needs a rebuild. I merged all three locally and ran every check on the result: everything passes.🤖 Generated with Claude Code