Skip to content

Add multichain namespace support documentation for wallet buttons#582

Merged
rtomas merged 2 commits intomainfrom
devin/1753194335-wallet-buttons-multichain-docs
Jul 25, 2025
Merged

Add multichain namespace support documentation for wallet buttons#582
rtomas merged 2 commits intomainfrom
devin/1753194335-wallet-buttons-multichain-docs

Conversation

@devin-ai-integration
Copy link
Copy Markdown
Contributor

Description

This PR adds comprehensive documentation for the new multichain namespace functionality for wallet buttons, based on the changes introduced in PR #4688 in the appkit repository.

Changes made:

  • Added namespace parameter documentation to useAppKitWallet hook examples in React and Next.js
  • Added namespace prop documentation to <appkit-wallet-button /> web component examples
  • Added namespace parameter documentation to createAppKitWalletButton function examples in JavaScript, Vue, Nuxt, and Svelte
  • Added multichain examples showing usage with 'eip155', 'solana', and 'bip122' namespaces
  • Added documentation tables explaining the namespace options and their descriptions
  • Updated 8 framework-specific documentation files for consistency

Files modified:

  • appkit/javascript/core/actions.mdx
  • appkit/react/core/hooks.mdx
  • appkit/react/core/components.mdx
  • appkit/next/core/hooks.mdx
  • appkit/next/core/components.mdx
  • appkit/vue/core/wallet-buttons.mdx
  • appkit/nuxt/core/wallet-buttons.mdx
  • appkit/svelte/core/actions.mdx

The documentation now provides clear examples of how developers can target specific blockchain namespaces when using wallet buttons, enabling better multichain support.

⚠️ Important Notes for Review:

  • Local build testing failed with pnpm run dev (though spell check passed), so please verify the documentation builds correctly in the preview
  • Examples are based on PR #4688 - please validate that the API usage examples are accurate
  • Multiple framework files were updated - please check for consistency in terminology and examples

Tests

  • Ran spell check successfully with pnpm run spell - no spelling errors found
  • Ran the changes locally with Mintlify and confirmed that the changes appear as expected (blocked by build issues)
  • Ran a grammar check on the updated/created content using ChatGPT

Direct link to the deployed preview files

Preview links will be available once CI completes successfully


Link to Devin run: https://app.devin.ai/sessions/1f5241d6058645ceb8de4fa30eec8815

Requested by: TomTom (tomas.rawski@reown.com)

- Add namespace parameter to useAppKitWallet hook examples in React and Next.js
- Add namespace prop to <appkit-wallet-button /> component examples
- Add namespace parameter to createAppKitWalletButton function examples
- Add multichain examples showing 'eip155', 'solana', and 'bip122' namespaces
- Add documentation tables explaining namespace options across all frameworks
- Update JavaScript, React, Next.js, Vue, Nuxt, and Svelte documentation

Based on PR #4688 in reown-com/appkit repository

Co-Authored-By: TomTom <tomtom@reown.com>
@github-actions
Copy link
Copy Markdown

@devin-ai-integration[bot] Please review the tone of voice for the content changes in this PR against Reown's brand guidelines.

📝 Content Review Request

Files to review: 8

  • appkit/javascript/core/actions.mdx
  • appkit/next/core/components.mdx
  • appkit/next/core/hooks.mdx
  • appkit/nuxt/core/wallet-buttons.mdx
  • appkit/react/core/components.mdx
  • appkit/react/core/hooks.mdx
  • appkit/svelte/core/actions.mdx
  • appkit/vue/core/wallet-buttons.mdx

Review focus:

  • Tone alignment with Reown's brand guidelines
  • Clear and accessible language for developers
  • Professional yet approachable communication
  • Consistent terminology usage

Guidelines summary:

  • Clear & Accessible: Translate complex ideas into approachable language
  • Professional yet Friendly: Maintain authority while being welcoming
  • Developer-Focused: Understand technical audience but remain inclusive
  • Avoid: Overly casual language, fear-based messaging, buzzwords, jargon without explanation
  • Embrace: Clear explanations, confident tone, transparency, respectful communication

Please analyze the content changes and provide constructive feedback on tone and voice alignment.

@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

@github-actions
Copy link
Copy Markdown

@devin-ai-integration[bot] Please review the tone of voice for the content changes in this PR against Reown's brand guidelines.

📝 Content Review Request

Files to review: 8

  • appkit/javascript/core/actions.mdx
  • appkit/next/core/components.mdx
  • appkit/next/core/hooks.mdx
  • appkit/nuxt/core/wallet-buttons.mdx
  • appkit/react/core/components.mdx
  • appkit/react/core/hooks.mdx
  • appkit/svelte/core/actions.mdx
  • appkit/vue/core/wallet-buttons.mdx

Review focus:

  • Tone alignment with Reown's brand guidelines
  • Clear and accessible language for developers
  • Professional yet approachable communication
  • Consistent terminology usage

Guidelines summary:

  • Clear & Accessible: Translate complex ideas into approachable language
  • Professional yet Friendly: Maintain authority while being welcoming
  • Developer-Focused: Understand technical audience but remain inclusive
  • Avoid: Overly casual language, fear-based messaging, buzzwords, jargon without explanation
  • Embrace: Clear explanations, confident tone, transparency, respectful communication

Please analyze the content changes and provide constructive feedback on tone and voice alignment.

@rtomas rtomas merged commit bd166a5 into main Jul 25, 2025
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