docs: redirect explorer submission page to WalletConnect dashboard

[devin-ai-integration]

Description

Replaces the full WalletGuide Submission page (cloud/explorer-submission.mdx) with a simple redirect to the WalletConnect Dashboard and a link to the WalletConnect WalletGuide Submission docs.

All previous subsections (Creating a New Project, Project Details, Project Submission, QA testing procedures, chain-specific tests, What's Next) have been removed, as this content now lives in the WalletConnect docs.

Link to Devin run: https://app.devin.ai/sessions/ad97c98ac5a44462b3bac1c8dee14077
Requested by: TomTom

Local preview

Verified locally with Mintlify dev server:

Notes for reviewers

• snippets/cloud/explorer-submission.mdx also contains similar (older) content but is not referenced anywhere in the codebase. It was left unchanged since it is unused.
• Please verify the two external links resolve correctly: WalletConnect Dashboard and WalletGuide Submission docs.

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 link to the deployed preview files

• WalletGuide Submission

[devin-ai-integration]

🤖 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]

@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: 1

• cloud/explorer-submission.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.