Help Information Architecture Plan

Goal: keep help easy to find in-app while moving long-form setup/troubleshooting to web docs.

Current in-app help surfaces

• Get help now screen: /home/support
• Contact/support screen content: direct channels and community links
• Connection diagnostics: /home/connection-diagnostics
• Legal/trust: /home/legal-trust
• New top app-bar Help action: opens https://emberdeck.xyz/appstart

Recommendation

Keep all current in-app help screens, but clarify their jobs:

1. Top app-bar Help (new):

   • Primary onboarding/startup path.
   • Fast link to "zero to hero" setup steps.

2. Get help now (/home/support):

   • Human support and community channels.
   • Keep this as contact/escalation, not deep technical docs.

3. Connection diagnostics (/home/connection-diagnostics):

   • Operational troubleshooting tool.
   • Link out to troubleshooting sections on web docs.

4. Legal/trust (/home/legal-trust):

   • Compliance/legal information only.

What to avoid

• Do not duplicate full startup instructions in multiple in-app screens.
• Do not mix legal/policy pages with troubleshooting steps.
• Do not rely on support contact as the first path for common setup issues.

Proposed content flow

• User clicks app-bar Help -> lands on /appstart.
• /appstart includes links to:
  • permissions,
  • events,
  • troubleshooting,
  • security model,
  • FAQ.
• If unresolved, user goes to /home/support for direct contact.

Verification after rollout

• Confirm Help action exists on primary app bars.
• Confirm URL opens externally on iOS/Android/Desktop.
• Confirm startup page includes route-based checks and validation checklist.
• Confirm support screen remains focused on channels, not duplicated docs.