feat(ui): integrate membership system into existing site
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 33
- Forks
- 104
- Avg merge
- 12h 3m
- Merged PRs (30d)
- 10
Description
Summary
Connect the membership system (auth, profiles, admin) to the existing US-RSE React app — update navigation, add sign-in/sign-up flows to the UI, and link profiles throughout the site.
Requirements
- Add Sign In / Sign Up buttons to the navbar (replace or complement "Join Us")
- Signed-in state: show user avatar + dropdown (profile, settings, sign out)
- Admin users see "Dashboard" link in their dropdown
- Link board member names on Governance/Board pages to their member profiles
- Add "View your profile" to the Community section
- Update footer with member-related links (Sign In, My Profile, Admin)
- Mobile menu: auth state reflected (sign in vs signed-in user)
- 404 page for invalid profile slugs
- Loading states for auth-dependent UI
Context
Parent issue: #1916
Depends on: #1918 (auth), #1919 (profiles) — this is the final integration step
Implementation Notes
- Nav component needs auth context to conditionally render sign-in vs avatar
- Consider a
<UserMenu>dropdown component for signed-in state - Board page photos can link to
/members/:slugonce profiles exist - This is the "glue" issue — it's about connecting pieces, not building new systems
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Nav component and auth context, then trace the Board/Governance pages, Community section, footer, and mobile menu. Review the auth and profiles work in #1918 and #1919 before connecting their existing pieces. Done means each listed auth, profile-linking, invalid-slug, and loading-state requirement works across desktop and mobile UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100