Skip to content

Rename SDK docs to MetaMask Connect#2749

Merged
shahbaz17 merged 21 commits intosdk-new-structurefrom
sdk-to-metamask-connect
Mar 11, 2026
Merged

Rename SDK docs to MetaMask Connect#2749
shahbaz17 merged 21 commits intosdk-new-structurefrom
sdk-to-metamask-connect

Conversation

@shahbaz17
Copy link
Member

@shahbaz17 shahbaz17 commented Mar 10, 2026

  • Rename the top-level docs from sdk to metamask-connect and update related content and config.
  • Updated docusaurus.config.js to point to the new path and sidebar (mm-connect-sidebar.js), added a client-redirects plugin to map existing /metamask-connect paths back to /sdk, and renamed LLMS output patterns and titles.
  • Adjusted internal documentation links (CardList, quickstarts, multichain/method refs) and updated versioned docs to use the new paths.
  • Minor docs formatting tweaks in CONTRIBUTING.md and many doc/asset files were moved/renamed to reflect the new structure.

Description

Issue(s) fixed

Fixes #

Preview

Checklist

  • If this PR updates or adds documentation content that changes or adds technical meaning, it has received an approval from an engineer or DevRel from the relevant team.
  • If this PR updates or adds documentation content, it has received an approval from a technical writer.

External contributor checklist

  • I've read the contribution guidelines.
  • I've created a new issue (or assigned myself to an existing issue) describing what this PR addresses.

Note

Medium Risk
Medium risk because it renames a major docs route (/sdk -> /metamask-connect) and adjusts sidebars/redirect rules; mistakes could cause broken links or navigation regressions across the site.

Overview
Renames the docs section formerly served at sdk to metamask-connect and updates Docusaurus config, navigation (footer, mobile menu, sub-nav), and announcement messaging to point at the new route.

Adds/updates redirect handling (Docusaurus client redirects plus expanded vercel.json redirects) to preserve legacy URLs, and refreshes cross-doc links and references (including versioned Smart Accounts Kit and Snaps docs) to use the new metamask-connect paths. Also replaces the old sdk intro/about pages with new MetaMask Connect pages (architecture, integration options, supported platforms) and updates LLM export patterns/titles accordingly.

Written by Cursor Bugbot for commit 45873db. This will update automatically on new commits. Configure here.

Signed-off-by: bgravenorst <byron.gravenorst@consensys.net>
Signed-off-by: bgravenorst <byron.gravenorst@consensys.net>
Signed-off-by: bgravenorst <byron.gravenorst@consensys.net>
Signed-off-by: bgravenorst <byron.gravenorst@consensys.net>
@shahbaz17 shahbaz17 requested review from a team as code owners March 10, 2026 10:23
@vercel
Copy link

vercel bot commented Mar 10, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
metamask-docs Ready Ready Preview, Comment Mar 11, 2026 7:57am

Request Review

Rename the top-level docs from `sdk` to `metamask-connect` and update related content and config. Updated docusaurus.config.js to point to the new path and sidebar (mm-connect-sidebar.js), added a client-redirects plugin to map existing /metamask-connect paths back to /sdk, and renamed LLMS output patterns and titles. Adjusted internal documentation links (CardList, quickstarts, multichain/method refs) and updated versioned docs to use the new paths. Minor docs formatting tweaks in CONTRIBUTING.md and many doc/asset files were moved/renamed to reflect the new structure.
Adjust various routing rules in vercel.json to reflect documentation reorganization. Key changes:
- Redirect several /metamask-connect/... sources to /sdk/... and vice versa where appropriate.
- Add new /sdk/connect/* mappings to corresponding /metamask-connect/evm/connect/quickstart/ routes (including wagmi, rainbowkit, connectkit, dynamic, web3auth, react-native, etc.).
- Consolidate wallet reference redirects to /metamask-connect/evm/connect/reference/json-rpc-api/ and add a wildcard mapping for JSON-RPC paths.
- Update destinations for supported-platforms, llm-prompt, and SDK reference pages; change some quickstart/partner destinations to quickstart.
- Remove obsolete multichain and duplicate snaps-development-guide redirects and adjust connect-extension destination.
These changes mirror a docs restructure to centralize SDK and Connect content under the Metamask Connect/EVm paths.
Signed-off-by: bgravenorst <byron.gravenorst@consensys.net>
Signed-off-by: bgravenorst <byron.gravenorst@consensys.net>
Signed-off-by: bgravenorst <byron.gravenorst@consensys.net>
@bgravenorst
Copy link
Contributor

bgravenorst commented Mar 10, 2026

General comment, we dont need the extra connect folder in /metamask-connect/multichain/connect/guides/sign-transactions/ it does'nt have any content and is redundant. So perhaps flatten to /metamask-connect/multichain/guides/sign-transactions/

It currently adds structure without meaning. Directories should exist because they group distinct content, and this change provides a shorter cleaner URL.

Fix links in src/pages/quickstart/builder/metamask-sdk/react/stepContent/connect.mdx to point to the EVM-specific documentation: update the JSON-RPC methods reference to /metamask-connect/evm/reference/json-rpc-methods and the batch-requests guide to /metamask-connect/evm/guides/metamask-exclusive/batch-requests so provider.request() documentation targets the correct pages.
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.

@shahbaz17 shahbaz17 merged commit 6ac476d into sdk-new-structure Mar 11, 2026
5 checks passed
@shahbaz17 shahbaz17 deleted the sdk-to-metamask-connect branch March 11, 2026 07:57
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.

2 participants