Skip to content

docs: add Multiwallet Linking page to accounts & authentication section#769

Merged
rtomas merged 2 commits intomainfrom
devin/1773936768-multiwallet-linking
Mar 19, 2026
Merged

docs: add Multiwallet Linking page to accounts & authentication section#769
rtomas merged 2 commits intomainfrom
devin/1773936768-multiwallet-linking

Conversation

@devin-ai-integration
Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration bot commented Mar 19, 2026

Description

Adds a new "Multiwallet Linking" documentation page under the Accounts & Authentication section in the AppKit Overview navigation. This page explains the feature, its use cases, benefits, and links to framework-specific hook docs for React, Next.js, and Vue.

Changes

  • New page: appkit/features/multiwallet-linking.mdx with Use Cases, Why use it, and Get Started sections
  • Navigation: Added appkit/features/multiwallet-linking to the "Accounts & Authentication" group in docs.json
  • Spell check: Added "Multiwallet" and "multiwallet" to .cspell.json

Things to verify during review

  • The anchor #useappkitconnections in each card link should be verified to exist on the target hook/composables pages. (Auto-review confirmed they exist on React hooks:691, Next.js hooks:627, Vue composables:374.)
  • Hook names referenced in the copy: useAppKitConnection (singular) & useAppKitConnections (plural) — confirm casing and naming are correct.
  • Original copy used British English "behaviour"; changed to American English "behavior" to match codebase conventions (smart-accounts-interaction.mdx uses "behavior"). Confirm this is acceptable.

Updates since last revision

  • Switched card href values from absolute URLs (https://docs.reown.com/...) to relative paths (/appkit/react/core/hooks#useappkitconnections) to match conventions in other overview pages and work correctly in preview deployments.
  • Changed "behaviour" → "behavior" (American English) for codebase consistency; removed "behaviour" from .cspell.json.

Tests

  • - Ran the changes locally with Mintlify and confirmed that the changes appear as expected.
  • - Ran a grammar check on the updated/created content using ChatGPT.

Direct links to the deployed changes in Mintlify.

Link to Devin session: https://app.devin.ai/sessions/090cbf19871e411a8a2a370964c4ea56

Co-Authored-By: Jem Conlon <jem@walletconnect.com>
@devin-ai-integration
Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@claude
Copy link
Copy Markdown

claude bot commented Mar 19, 2026

Claude finished @devin-ai-integration[bot]'s task in 4s —— View job


Review

  • Gather context and read changed files
  • Check link anchors and target pages
  • Verify URL patterns vs codebase conventions
  • Tone of voice compliance check
  • Data classification check
Found 2 issue(s)

Issue 1: Absolute URLs in Card hrefs should be relative paths

ID: multiwallet-linking-absolute-urls-a3f1
File: appkit/features/multiwallet-linking.mdx:32-41
Severity: MEDIUM
Category: code_quality

Context:

  • Pattern: Card href values use full absolute URLs (https://docs.reown.com/appkit/react/core/hooks#useappkitconnections)
  • Risk: Every other feature overview page in appkit/features/ uses relative paths (e.g. /appkit/react/core/hooks#useappkitconnections). Absolute URLs break in preview/staging deployments and create maintenance burden if the domain changes.
  • Impact: Links will not resolve correctly in Mintlify preview deployments; redirects/domain changes require content edits.
  • Trigger: Every page load in non-production environments.

Recommendation: Use relative paths consistent with swaps.mdx, multichain.mdx, onramp.mdx, etc.:

<Card icon="react" href="/appkit/react/core/hooks#useappkitconnections">
<Card icon="square-n" href="/appkit/next/core/hooks#useappkitconnections">
<Card icon="vuejs" href="/appkit/vue/core/composables#useappkitconnections">

Fix this →


Issue 2: British English "behaviour" inconsistent with codebase standard

ID: multiwallet-linking-spelling-behaviour-c2e8
File: appkit/features/multiwallet-linking.mdx:24
Severity: LOW
Category: code_quality

Context:

  • Pattern: "behaviour" (British English) used twice on line 24; smart-accounts-interaction.mdx uses American "behavior".
  • Risk: Inconsistent spelling within the same content section; the word was added to .cspell.json to suppress the spell-check failure rather than aligning with the existing convention.
  • Impact: Minor inconsistency; no functional impact.

Recommendation: Change to American English to match the existing codebase convention:

- **Deeper insights into user behavior**: with multiwallet linking, users don't need to make 2 profiles to use 2 wallets, removing fragmentation and giving you better insights into user behavior.

Also remove "behaviour" from .cspell.json words list.

Additional notes (non-blocking):

  • #useappkitconnections anchors confirmed present in all three target pages (React hooks:691, Next.js hooks:627, Vue composables:374) ✅
  • Hook names useAppKitConnection (singular) and useAppKitConnections (plural) are both correct ✅
  • Tone of voice: content is appropriately informative and professional for developer documentation ✅
  • Data classification: no sensitive data patterns detected in the changed files ✅
  • The "Get Started" copy refers to "Hooks" generically but Vue uses composables — minor, but could say "hooks and composables" for accuracy

Comment thread appkit/features/multiwallet-linking.mdx Outdated
Comment thread appkit/features/multiwallet-linking.mdx Outdated
Co-Authored-By: Jem Conlon <jem@walletconnect.com>
@rtomas rtomas merged commit 061230a into main Mar 19, 2026
4 checks 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