In-app help / FAQ system

[truthixify]

Labels: Stellar Wave, ux, feature, docs, drips, help-wanted, good-first-issue
Tier: M (2–4 days)
Type: UX / docs

Context

Today, a confused demo user has to leave the app and read the docs site. That's a real bounce risk. We should put help one click away — a small floating "?" button that opens an overlay with the FAQs most relevant to where the user is right now.

Scope

1. Floating help button in bottom-right corner (above any wallet widget). Subtle, easy to dismiss. Keyboard-accessible.
2. Help overlay opens from the button:
   • Closes via X, Esc, or clicking outside.
   • Contains a search input at top.
   • Below: a list of FAQ entries grouped by category:
     • Getting started: "What is a stealth address?", "Why do I need to sign a message?", "Why Freighter / Albedo?"
     • Stellar specifics: "What's a .wraith name on Stellar?", "Why can't I send under 0.001 XLM?", "What's a base reserve?"
     • Privacy: "Is this actually private?", "Does Wraith see my payments?", "What does the demo log?"
     • Troubleshooting: "Scan returned no results — why?", "Withdraw failed — why?", "I lost my stealth key — what now?"
3. Context-awareness:
   • On the Send page, "Sending" FAQs surface first.
   • On the Receive page, "Receiving" FAQs surface first.
4. Content:
   • Each FAQ entry has a question + 2-3 paragraph answer.
   • Links to docs for the deep dive ("Learn more →").
5. Content lives in src/help/faq.ts as a typed array. Easy to edit, easy to translate (coordinate with the future i18n work).

Acceptance criteria

• Help button visible across all pages.
• Overlay opens with proper a11y (focus trap, Esc to close, ARIA labels).
• At least 15 FAQ entries written.
• Search filters entries in real time.
• Context-awareness verified — Send and Receive pages prioritize different entries.

Why good-first-issue

The infrastructure is straightforward (overlay + search). Most of the work is writing — and the writing benefits a new contributor by forcing them to learn the protocol.

[Kaycee276]

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

Hi maintainer, can i be assigned to this?

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

[boalambo]

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

I would love to fix the issue, kindly assign me. Thank you

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

[drips-wave]

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

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