[FE-15] Build the new user onboarding flow

[mftee]

Overview

Build a multi-step onboarding flow shown to new users after their first login, guiding them through uploading their first document inside frontend/cmmty/.

Acceptance Criteria

• Create frontend/cmmty/pages/onboarding/ with the multi-step flow
• Step 1: Welcome and platform overview
• Step 2: Prompt to upload first document (with file picker)
• Step 3: Explain the risk assessment process
• Step 4: Explain Stellar verification and what the tx hash means
• Include Skip and Back navigation
• Only show to users who have not completed onboarding (localStorage flag)

Contribution Folder

All files must be placed inside frontend/cmmty/. Do not modify any file outside this folder.

How to Contribute

Comment on this issue to express interest, fork the repo, build inside frontend/cmmty/ only, and open a PR targeting main.

[Fale1278]

@Fale1278 has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

I’d love to take this on. I have experience building guided onboarding experiences and handling file-upload workflows, so I can create a smooth introduction for new users within the community folder.

Guided Multi-Step UI: I’ll build the onboarding flow in frontend/cmmty/pages/onboarding/, structuring it into four clear steps:

Welcome: A high-level overview of the platform's value.

Upload: An integrated file picker for their first document.

Risk Education: A concise explanation of how risk assessments are handled.

Stellar Integration: A technical primer on verification and the importance of the transaction hash.

State & Navigation: I’ll implement a robust navigation system with Skip and Back functionality. I'll use a localStorage flag to ensure the flow only triggers for new users, preventing repetitive interruptions for returning members.

Scoped Implementation: In strict accordance with the contribution guidelines, all components, logic, and styling will be contained entirely within frontend/cmmty/, ensuring a clean and independent pull request.

ETA: Less than 24 hours.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Fale1278 to this issue.

[Uyoxy]

@Uyoxy has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

can i work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Uyoxy to this issue.

[drips-wave]

Congratulations, @Uyoxy! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @Uyoxy: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @Uyoxy as part of the Stellar Wave Program's 4th Wave 🥳

😎 @Uyoxy: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.