Skip to content

Wire the landing CTAs to the animal and foster routes - #249

Merged
FoxMon merged 1 commit into
developfrom
landing-routing
Aug 2, 2026
Merged

Wire the landing CTAs to the animal and foster routes#249
FoxMon merged 1 commit into
developfrom
landing-routing

Conversation

@FoxMon

@FoxMon FoxMon commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

What

The landing page's call-to-action buttons rendered but had no navigation. This wires them:

Button Destination
우리 가족 찾기 (hero primary) /animals
임시보호 알아보기 (hero secondary) /foster
우리 가족 만나러 가기 (closing CTA) /animals

Uses the app's navigate() pattern (as in NotFoundState / VolunteerPage). A guest who follows a CTA hits the auth gate and is sent to login, like any other consumer route; an authed visitor lands on the target page.

The animal cards in the '지금 만날 수 있는 친구들' section are static fixtures with no ids, so they aren't individually linkable — left as-is.

Verify

typecheck, lint, and the production build pass. Adds a landing e2e that logs in and follows the hero + closing CTAs through to /animals; the full flow passes locally.

The hero and closing call-to-action buttons rendered but went nowhere.
Point 우리 가족 찾기 and 우리 가족 만나러 가기 at the animal list, and
임시보호 알아보기 at the foster route, via navigate(). A guest following
them is sent through the auth gate to login, as with any consumer route.

Adds an e2e that follows the hero and closing CTAs to /animals.
@FoxMon
FoxMon merged commit 0977b4c into develop Aug 2, 2026
5 checks passed
@FoxMon
FoxMon deleted the landing-routing branch August 2, 2026 14:09
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.

1 participant