Skip to content

docs: user-first use cases + simplified entry points#1

Merged
TheNewAutonomy merged 1 commit intomainfrom
docs/use-cases-user-first
Mar 4, 2026
Merged

docs: user-first use cases + simplified entry points#1
TheNewAutonomy merged 1 commit intomainfrom
docs/use-cases-user-first

Conversation

@TheNewAutonomy
Copy link
Member

Summary

  • Add a new Use cases (for everyone) section that explains Catalyst benefits without jargon (send money, games/assets, social, plain-English overview).
  • Add a new quickstart: Quickstart: I want to use Catalyst apps.
  • Update the homepage CTAs/tiles to lead with everyday user tasks first.
  • Node operator docs: add a no-build path via release binaries (keep source-build path).
  • Builder docs: add a clear note to keep non-builders out of RPC internals.

Why

The docs were strong for operators/builders, but lacked a front door for everyday users. This starts shifting the docs toward user outcomes and use cases, with progressive disclosure.

Test plan

  • npm run build

Follow-ups

  • Add screenshots and UX walkthroughs for wallet/explorer/faucet (tool agents).
  • Expand the “Use apps” flow once app-store/dApp directory exists.

Made with Cursor

- Add new Use cases section (send money, games/assets, social, plain-English overview)
- Add quickstart for using apps
- Reframe homepage/entry points toward everyday users
- Add no-build path for node operators (release binaries)
- Add builder-facing notes to keep non-builders out of RPC internals

Made-with: Cursor
@TheNewAutonomy TheNewAutonomy merged commit 336c798 into main Mar 4, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant