Skip to content

fix: landing page CTA respects auth state (closes #15) - #18

Merged
nycomp merged 1 commit into
mainfrom
fix/landing-cta-signed-in
Oct 1, 2026
Merged

nycomp merged 1 commit into
mainfrom
fix/landing-cta-signed-in

Conversation

@nycomp

@nycomp nycomp commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

Closes #15.

index.html hardcoded the Sign In CTAs, so a signed-in user landing on / saw "Sign In to Get Started" in the hero — and "Sign In Now" in the bottom CTA section — while base.html's navbar already showed their identity. Both sections now branch on g.user (same idiom the navbar uses):

  • signed in → Go to Dashboard (/dashboard) in the hero; bottom section becomes "Welcome Back / Go to your dashboard…" with the same button
  • signed out → unchanged Sign In to Get Started / Sign In Now

Verification (local, real dev login session)

  • Signed-out GET /: Sign In CTAs only, no "Go to Dashboard".
  • Signed-in GET / (live login session in the Flask session): hero and bottom both render "Go to Dashboard" → /dashboard; "Sign In to Get Started" and "Sign In Now" are gone from the page.

index.html hardcoded the Sign In CTAs, so a signed-in user landing on /
saw "Sign In to Get Started" in the hero (and "Sign In Now" at the
bottom) while the navbar already showed their identity. Branch both CTAs
on g.user: signed in -> Go to Dashboard (/dashboard), signed out ->
current Sign In CTAs.
@nycomp
nycomp merged commit c2c341e into main Oct 1, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Landing page shows \u201cSign In to Get Started\u201d while the user is signed in

2 participants