Skip to content

docs(wcp): add Wallet Coverage page#54

Open
riveign wants to merge 3 commits into
mainfrom
docs/wcp-wallet-coverage
Open

docs(wcp): add Wallet Coverage page#54
riveign wants to merge 3 commits into
mainfrom
docs/wcp-wallet-coverage

Conversation

@riveign
Copy link
Copy Markdown
Contributor

@riveign riveign commented May 19, 2026

Summary

  • Adds new payments/wallet-coverage.mdx page covering: every WalletConnect-compatible wallet works with WCP (700+), the Certified subset (Rounds 1 + 2, 28 wallets) in a table, Phantom + Solflare for Solana (explicitly not Certified), a chain-dependency warning that cross-links to Token and Chain Coverage, and WalletGuide CTAs (full directory + Certified filter).
  • Nav updated in both version blocks of docs.json: Latest (2026-02-18) and Preview (2026-02-19.preview). New entry placed immediately after payments/token-and-chain-coverage.
  • Why: customers + Sales kept asking "which wallets work with WCP?" — page sets the "all of them" baseline, then surfaces Certified as the reviewed subset and points at WalletGuide as the live source of truth.

Preview

Mintlify preview link will appear in the PR checks once the preview build runs.

Sentinel review

Verdict: PASS-WITH-NITS. All four nits applied in this PR:

  • Nit 1 — Phantom + Solflare moved from bullets to a parallel Solana table, visually consistent with the Certified table.
  • Nit 2 — Added Last reviewed: 2026-05-19 stamp above the Certified table, with re-link to the live WalletGuide Certified filter as the canonical source.
  • Nit 3 — Added a second <Note> below the Certified table explicitly addressing absent-from-Certified wallets (Coinbase Wallet called out by name) and redirecting to WalletGuide.
  • Nit 4mise.toml (pre-existing local node-version pin, unrelated to this work) was NOT staged. Commit contains only the two intended files.

Test plan

  • Mintlify preview link in PR checks loads /payments/wallet-coverage
  • Sidebar nav shows "Wallet Coverage" entry directly below "Token and Chain Coverage" in the WalletConnect Pay group
  • Certified wallets table renders with 28 rows + the "Last reviewed" stamp
  • Solana wallets table renders with Phantom + Solflare as linked rows
  • Chain-dependency <Warning> block renders and the link to /payments/token-and-chain-coverage resolves
  • Both <CardGroup> CTAs at the bottom of the page link to WalletGuide and the Certified filter URL respectively
  • Same nav placement verified in the Preview version block (2026-02-19.preview)

🤖 Generated with Claude Code

Adds a new page below Token and Chain Coverage covering:
- WalletConnect-compatible wallets (700+)
- Certified wallets table (Rounds 1 + 2)
- Phantom + Solflare as Solana-recommended (not Certified)
- Chain-dependency warning cross-linking Token and Chain Coverage
- WalletGuide CTA with certified filter URL

Nav updated in both Latest (2026-02-18) and Preview
(2026-02-19.preview) version blocks.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@mintlify
Copy link
Copy Markdown

mintlify Bot commented May 19, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
wc-pay-docs 🟢 Ready View Preview May 19, 2026, 4:21 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

- Replaces Certified table + Solana subsection with single
  "Top wallets" list (usage + volume) covering Round 1+2 wallets
  plus Phantom, Solflare, Rainbow.
- Removes per-wallet chain column — chain coverage stays as a
  callout cross-linking Token and Chain Coverage.
- Drops "What does Certified mean?" explainer.
- WalletGuide CTA simplified to main URL.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Removes description frontmatter, the "no separate WCP-only
allow-list" sentence, and the last-reviewed stamp per editorial
feedback. WalletGuide CTA retained.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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