fix: unify back navigation copy on meetup pages - #54
Open
Elydeboss wants to merge 1 commit into
Open
Conversation
FrankezeCode
requested changes
Aug 3, 2026
FrankezeCode
left a comment
Collaborator
There was a problem hiding this comment.
Thanks for picking this up, @Elydeboss — the Builder Circles back link is a solid fix 👍
What works well
/meetup/[meetupId]/circles→ “Back to RSVP” with link to/meetup/[meetupId]matches the user flow.
Please update before merge
-
Remove unrelated files from this PR:
.nvmrcpackage-lock.json(large lockfile churn isn’t needed for a nav copy fix)
Tip: if those changes came from running
npm installlocally, you can reset them with:git checkout main -- package-lock.json git rm --cached .nvmrc # if .nvmrc wasn't on main
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.
I fixed navigation hierarchy inconsistencies in the meetup flow by standardizing back link terminology and destinations to follow proper parent-child navigation patterns.
What Changed
Problem: The meetup pages (/meetup/[meetupId] and /meetup/[meetupId]/circles) used inconsistent navigation:
Confusing "Back to Passport" terminology
Flat navigation structure (both jumped to /meetup)
Didn't follow logical parent-child hierarchy used elsewhere in the app
Solution: Implemented hierarchical navigation matching the app's organizer flows:
/meetup/[meetupId]/circles now goes back to /meetup/[meetupId] (RSVP page)
/meetup/[meetupId] now goes back to /meetup (meetup list)
Updated terminology to be more contextually appropriate
Files Modified
src/app/meetup/[meetupId]/page.tsx - Updated back link text and destination
src/app/meetup/[meetupId]/circles/page.tsx - Updated back link text and destination.
How to Test
Test RSVP Page Navigation:
Navigate to /meetup/[some-meetup-id]
Verify back link shows "← Back to meetups"
Click back link and confirm it navigates to /meetup
Test Builder Circles Navigation:
Navigate to /meetup/[some-meetup-id]/circles
Verify back link shows "← Back to RSVP"
Click back link and confirm it navigates to the RSVP page for that meetup
Test Complete User Flow:
Navigate: Home → /meetup → RSVP → Circles
Test step-back navigation: Circles → RSVP → Meetups → Home
Verify each back link works correctly and follows proper hierarchy
Verify Visual Consistency:
Confirm styling matches other pages (blue text, proper spacing)
Check hover states work correctly
Ensure no visual regressions.