Document backend dependency matrix for frontend features

[josephchimebuka]

Problem

Many frontend issues depend on backend endpoints that may not be ready. Contributors need a matrix showing what works without backend vs what requires it.

Scope

• Add a table in README or docs/BACKEND_DEPENDENCIES.md
• Map routes/components to required endpoints/events

Acceptance criteria

• Matrix covers Landing, /dashboard, /play, Leaderboard, Learn, wallet auth
• Notes which features can be built with mocks

Files

• README.md or docs/BACKEND_DEPENDENCIES.md

[Benedict315]

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

Hello please assign me to this issue

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

[42natus]

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

I'd love to work on this, please assign

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

[Ejere]

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

Hi, my name is Ejere, and I am a fullstack and smart contract developer skilled in React, Next.js, JavaScript, TypeScript, Tailwind CSS, and Soroban. For this task, I will:

1. Create a backend dependency matrix in README.md or docs/BACKEND_DEPENDENCIES.md that clearly maps frontend routes and components to their required backend endpoints and events.
2. Document dependencies for the Landing page, /dashboard, /play, Leaderboard, Learn, and wallet authentication, making it easy for contributors to understand feature readiness.
3. Identify which frontend features can be developed and tested using mocked data versus those that require live backend services, reducing contributor uncertainty.
4. Ensure the documentation is well-structured, consistent with the repository's style, and easy to maintain as backend capabilities evolve.

ETA: 10 hours

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

[drips-wave]

Congratulations, @42natus! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @42natus: 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 🌊