Repository navigation
Concepts docs: App routing & conversation UI architecture #463
Description
Write apps/web/docs/concepts-app-routing.md explaining the Next.js App Router structure under app/, the authenticated app/app/ shell and its child routes (conversations, devices, messages, profile, proposals, search, treasury), and how the conversation view composes its message list, input, and safety-number UI.
Acceptance criteria:
- The route tree is documented with a one-line purpose for each top-level route under
app/app/ - The conversation route's composition (which components/hooks it pulls together) is documented at a level that orients a new contributor
- Written against the routing structure as it exists after the route-consolidation work
Activity
Toyinoje commentedon Jul 29, 2026
@Toyinoje has applied to work on this issue as part of the Stellar Wave Program's 7th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Toyinoje to this issue.
drips-wave commentedon Jul 29, 2026
Congratulations, @psalmuel3! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.
🧑💻 @psalmuel3: 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 🌊
kareemijaola123 commentedon Sep 23, 2026
@kareemijaola123 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @kareemijaola123 to this issue.
Annoor24 commentedon Sep 23, 2026
@Annoor24 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Annoor24 to this issue.
nugarjr5 commentedon Oct 21, 2026
@nugarjr5 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @nugarjr5 to this issue.
G-ELM commentedon Oct 22, 2026
@G-ELM has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @G-ELM to this issue.
drips-wave commentedon Oct 22, 2026
Congratulations, @G-ELM! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @G-ELM: 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 🌊
github-actions commentedon Oct 22, 2026
Closed by #684, merged into
dev.drips-wave commentedon Oct 22, 2026
This issue has been completed by @G-ELM as part of the Stellar Wave Program's 10th Wave 🥳
😎 @G-ELM: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, 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.