Tier: M (2-4 days) Type: writing
Context
Developers arriving at docs.usewraith.xyz today have to assemble a working Stellar flow from four different pages. The number-one drop-off in dev tooling is the gap between landing page and first successful payload. Close it with one comprehensive page.
Scope
Write docs/guides/stellar-quickstart.mdx covering:
- Prerequisites (Node 22+, pnpm, Freighter, friendbot)
- Install
@wraith-protocol/sdk + @stellar/stellar-sdk + @stellar/freighter-api
- Connect Freighter, sign
STEALTH_SIGNING_MESSAGE, derive keys, render meta-address
- Register a
.wraith name
- Send to meta-address or
.wraith name
- Scan + receive
- Withdraw
- Common errors expandable section
- Links to deeper guides
Acceptance criteria
Files to start with
- New:
docs/guides/stellar-quickstart.mdx
docs/getting-started.mdx (style reference)
- Demo source
demo/src/components/Stellar*.tsx (working flow reference)
Tier: M (2-4 days) Type: writing
Context
Developers arriving at docs.usewraith.xyz today have to assemble a working Stellar flow from four different pages. The number-one drop-off in dev tooling is the gap between landing page and first successful payload. Close it with one comprehensive page.
Scope
Write
docs/guides/stellar-quickstart.mdxcovering:@wraith-protocol/sdk+@stellar/stellar-sdk+@stellar/freighter-apiSTEALTH_SIGNING_MESSAGE, derive keys, render meta-address.wraithname.wraithnameAcceptance criteria
stellar-quickstart.mdxcommitted and added todocs.jsonnavFiles to start with
docs/guides/stellar-quickstart.mdxdocs/getting-started.mdx(style reference)demo/src/components/Stellar*.tsx(working flow reference)