[UX]: streamline onboarding from landing page to dashboard connection

[MatrixAdventurer]

Summary

During real onboarding, the biggest friction was not core functionality but the path from landing page -> email login -> dashboard -> connect tool.

Instead of treating these as separate small UI issues, I think they should be handled as one onboarding flow improvement.

Main friction points observed

1. Landing page CTA still feels pre-launch

If the product/dashboard is already live, a Join waitlist style CTA creates confusion and lowers confidence.

Suggested change: use a direct entry CTA such as Open Dashboard.

2. Email-based access feels broken when mail lands in spam/junk/promotions

Users may assume the product failed when the email was actually delivered but filtered.

Suggested change: after sending email, clearly show guidance like:

• Check Spam / Junk / Promotions
• Resend email
• Use another email

3. Dashboard should expose connection details immediately

For technical users, the first thing they need is:

• API URL
• API key

If those are buried, the onboarding flow feels indirect.

Suggested change: add a clear Connect / API Access / Quick Start section with:

• API base URL
• API key create/copy
• minimal copy-paste examples

4. Git for Memory should reuse the signed-in account email

If the user is already authenticated in dashboard, asking them to re-enter the same email again adds unnecessary friction.

Suggested change: prefill or automatically reuse the signed-in email.

Why this should be treated as one issue

These are all parts of the same first-run conversion path:

1. decide to enter
2. receive login email
3. enter dashboard
4. find credentials
5. connect tool
6. enable Git for Memory

Optimizing them together will likely improve activation much more than treating each as an isolated UI tweak.

Suggested implementation priority

1. Replace outdated waitlist CTA with direct dashboard entry
2. Add explicit email delivery guidance in login flow
3. Add highly visible Connect / API Access section in dashboard
4. Reuse signed-in email in Git for Memory onboarding

[MatrixAdventurer]

I've broken this onboarding feedback into two concrete follow-up UX tasks from the same real onboarding session:

• [UX]: add a clearer first-run onboarding section to the dashboard #124 — clearer first-run onboarding section on the dashboard
• [UX]: make onboarding and dashboard errors more actionable #125 — more actionable onboarding/dashboard errors

Suggested structure:

• Keep [UX]: streamline onboarding from landing page to dashboard connection #123 as the umbrella onboarding-flow issue
• Track [UX]: add a clearer first-run onboarding section to the dashboard #124 and [UX]: make onboarding and dashboard errors more actionable #125 as concrete implementation slices under it

This should keep discussion centralized while still giving the team shippable units.

[MatrixAdventurer]

Opened PR #128 for the parts of onboarding friction that can be fixed directly in this repo today, specifically on the OpenClaw plugin/docs path (clearer first-run guidance, cleaner setup docs, more actionable health/setup messaging).

[MatrixAdventurer]

Status update: PR #128 has been closed as superseded by current main, because the repo-local OpenClaw plugin/docs changes from that PR were largely absorbed already.

Keeping this issue open because the main onboarding problems described here are still product/dashboard/website flow issues, not fully resolved repo-local code issues.

[MatrixAdventurer]

Additional context: current Memoria Cloud health also appears degraded (see #129), which may be compounding onboarding friction for cloud users.

[MatrixAdventurer]

Triage note: keeping this as the onboarding umbrella. Current shape seems to be: #123 = end-to-end onboarding flow / activation umbrella, #124 = dashboard first-run / get-started surface, #125 = actionable onboarding/dashboard error messaging. The earlier repo-local OpenClaw/plugin/doc slice was partially handled separately, but the product/dashboard/website onboarding flow still belongs here as the parent thread.