[FEAT] Implement "Invite Member" Link Generation and Deep Linking

[Queenode]

🟡 Priority: High
Difficulty: Hard
Estimated Effort: 3-4 days
Relevant Files: src/app/invite/[code]/page.tsx, src/components/groups/InviteButton.tsx
Labels: enhancement, priority:high, feature

Requirements

1. Dynamic Invite Links

   • From the Group Dashboard, users click "Invite Member". This must generate a unique, short URL (e.g., kolo.app/invite/abc123xyz).
   • Implement the Share API on mobile devices to easily copy the link or send via WhatsApp.

2. Deep Linking / Onboarding Router

   • When a non-authenticated user clicks the link, they must be routed through the Signup flow first, and then automatically redirected back to the specific Group Join confirmation page without losing context.

---

[OluRemiFour]

Hi Maintainer,
Interested in working on this issue. I'll implement the requested changes and ensure everything is properly tested before submission.

[Calebstack]

Hi, I'd like to work on this issue. I've gone through the description and acceptance criteria and I'm confident I can deliver it. I'll make sure every acceptance criterion is met and submit a clean, tested PR. Please assign it to me.

[Primex-hub]

I would love to solve this issue and I can submit within 24hrs

[adetomiwa21]

Hello maintainer, I'd like to work on this issue.
I've built invite and referral link systems before so I'm familiar with both the link generation side and the redirect-after-auth pattern this requires.
I've looked through the repo and the relevant files. My plan:
For link generation, I'll add an endpoint that creates a unique short code tied to the group, stores it, and returns the full invite URL. In InviteButton.tsx I'll call the Web Share API on mobile so users can send it directly via WhatsApp or copy it, with a clipboard fallback for browsers that don't support the Share API.
For the deep linking flow, when an unauthenticated user hits /invite/[code], I'll store the invite code in a session or query param before redirecting them into the signup flow, then after successful auth redirect them back to the group join confirmation page with the code intact. The tricky part is making sure the context survives the full auth redirect cycle without getting dropped. I'll handle that by persisting the destination in the URL itself through each step of the signup flow rather than relying on session state, which tends to be more reliable across mobile browsers.
I'll test: authenticated users land directly on the join page, unauthenticated users complete signup and land on the correct group without losing context, invalid or expired codes show a clear error, and the Share API falls back cleanly on desktop.
Ready to start once assigned.

[grantfox-oss]

🦊 GrantFox — @adetomiwa21 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #16)
2. Your PR will be reviewed by the Kolo-Org maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@adetomiwa21's PR #19 was approved and merged by @Queenode.

🏆 @adetomiwa21: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (83 total points). Track your full progress on GrantFox.

👏 Great work, @adetomiwa21! Keep contributing to Kolo-Org.