UX: collapse /signup into /signin (one front door)#136
Merged
Conversation
Sessions made /signup and /signin functionally identical — both create an account on first use of the magic-link form. The two pages just encoded a fake new-vs-returning distinction the backend no longer has. - /signup directory removed; FreeSignupForm component removed (only /signup used it). - /signin page absorbs the secondary "Prefer the CLI?" install snippet so CLI-first users still have a path without a separate page. - next.config.ts adds a 301 redirect /signup → /signin so inbound links and SEO equity survive. - Navbar collapses to a single CTA: "Sign in" when signed-out, "Account" when signed-in. Drops the misleading "Get API Key" button (it didn't actually hand you a key — three clicks + an email round-trip to mint one). - Internal references updated: pricing-section Free CTA → /signin, welcome page "See all commands" → "Sign in" → /signin. Out of scope but noted for follow-up: app/page.tsx and docs/manual-setup/page.tsx still mention the deleted POST /v1/auth/signup endpoint in docs/code samples. Worth fixing in a separate doc-drift pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
/signupand/signinare functionally identical — both create an account on first use of the magic-link form. The two pages just encoded a fake new-vs-returning distinction the backend no longer has./signin./signup301-redirects there for SEO / inbound links.What changed
marketing/src/app/signup/page.tsx+marketing/src/components/free-signup-form.tsx(FreeSignupForm was only used by/signup)./signupso CLI-first users still have a path without a separate page./signup → /signin.pricing-section.tsxFree tier CTA →/signin;welcome/page.tsx"See all commands" → "Sign in" →/signin.Out of scope (noted for follow-up)
marketing/src/app/page.tsxandmarketing/src/app/docs/manual-setup/page.tsxstill mention the deletedPOST /v1/auth/signupendpoint in docs / code samples. Same doc-drift category; worth a separate small PR.Test plan
/welcome"Sign in" link → `/signin`🤖 Generated with Claude Code