feat: change landing hero CTA to registration #146
No reviewers
Labels
No labels
domain:backend
domain:devops
domain:frontend
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/westside-landing!146
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "144-landing-hero-cta-registration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Changes
src/routes/(public)/+page.svelte: changed hero-cta div from single informational button to primary registration CTA + secondary learn more linkTest Plan
Review Checklist
Related Notes
forgejo_admin/westside-app #144-- the Forgejo issue this PR implementswestside-app-- the project this work belongs toCloses #144
PR #146 Review
DOMAIN REVIEW
Stack: SvelteKit / CSS (static markup change)
This is a minimal, well-scoped change: 1 file, +2/-1 lines. The hero CTA in
src/routes/(public)/+page.sveltewas changed from a single informational link ("Learn About Our Program" -> /about) to a primary registration CTA ("Register Your Player" -> /register) with a secondary "Learn More" link to /about.Verified:
/registeris inPUBLIC_APP_ROUTES(src/routes/(app)/+layout.svelte:26) -- safe for unauthenticated visitorsbtn-secondaryis defined insrc/app.css:224with proper background, color, and hover state.hero-ctausesflex-direction: column; gap: 0.5rem; max-width: 320px-- handles two stacked buttons cleanly/register,/about) are valid existing routesAccessibility: Both links use semantic
<a>elements with descriptive text. The primary/secondary visual hierarchy (btn-primary vs btn-secondary) provides clear affordance for the conversion funnel.BLOCKERS
None.
This is a static markup change with no new functionality, no user input handling, no dynamic behavior, and no security surface. The BLOCKER criteria (tests, input validation, secrets, DRY) do not apply.
NITS
None. The change is clean and minimal.
SOP COMPLIANCE
144-landing-hero-cta-registrationfollows{issue}-{kebab-case})Closes #144presentPROCESS OBSERVATIONS
Clean single-purpose PR. Low change failure risk -- static markup only, no logic changes. Good conversion funnel improvement (informational CTA -> lead generation CTA) while preserving the informational path as secondary.
VERDICT: APPROVED