docs: update WalletGuide submission page to match new dashboard UI

walletguide/explorer-submission.mdx

@@ -13,13 +13,13 @@ However, doing so ensures that your project is listed under [WalletGuide](https:
 
 First, open the WalletConnect Dashboard by navigating to [dashboard.walletconnect.com](https://dashboard.walletconnect.com/?utm_source=blog&utm_medium=devrel&utm_campaign=conversion) and signing in. If you don’t have an account yet, please create one before proceeding.
 
-- Once you're logged in, go to the "**Projects**" section under **Cloud** and click on "**+ Project**".
+- Once you're logged in, navigate to your team view and click the **"+ Project"** button.
 
   <Frame>
     <img src="/images/cloud/1.png" />
   </Frame>
 
-- Give a suitable name for your project, select Wallet (WalletKit) and click the "Create" button. You can change the name for your project later.
+- Select **"Wallet"**, enter a project name, and click **"Add"**.
 
   <Frame>
     <img src="/images/cloud/2.png" />
@@ -28,46 +28,85 @@ First, open the WalletConnect Dashboard by navigating to [dashboard.walletconnec
 
 ## Project Details
 
-- Click on “WalletGuide” to proceed to fill in the details of your wallet.
+- From the project Dashboard, click on the **"WalletGuide"** tab in the top navigation.
 
   <Frame>
     <img src="/images/cloud/3.png" />
   </Frame>
 
-- You will now see an option to publish your wallet to WalletGuide. Click "Publish" to proceed.
+- Click **"Start submission"** to begin the submission wizard.
 
   <Frame>
     <img src="/images/cloud/4.png" />
   </Frame>
 
-- You will now see a form to fill in the details of your wallet as shown below.
-
-| Field                        | Description                                                                 | Required |
-|------------------------------|-----------------------------------------------------------------------------|----------|
-| Name                         | The name to display in the explorer                                        | yes      |
-| Description                  | A short description explaining your project (dapp/wallet)                 | yes      |
-| Type                         | Whether your project is a dapp or a wallet                                | yes      |
-| Category                     | Appropriate category for your project. This field is dependent on the type of your project | yes      |
-| Homepage                     | The URL of your project                                                   | yes      |
-| Web App                      | The URL of your web app. This field is only applicable for dapps         | yes      |
-| Chains                       | Chains supported by your project                                         | yes      |
-| Logo                         | The logo of your project. Further requirements are provided in the explorer submission form | yes      |
-| Testing Instructions         | Instructions on how to test your Reown Integration                       | yes      |
-| Download Links               | Links to download your project (if applicable)                           | no       |
-| Mobile Linking               | Required for mobile wallets targeting AppKit. Deep Link is recommended over Universal Link | no       |
-| Desktop Linking              | Required for desktop wallets targeting AppKit.                          | no       |
-| Injected Wallet Identifiers  | Required for injected wallets targeting AppKit. RDNS (from EIP-6963 metadata) is recommended over Provider Flags(Legacy) | no       |
-| Metadata                     | User-facing UI metadata for your project. Only Short Name is required.   | no       |
+## Project Submission
 
+The submission is a multi-step wizard. Follow each step to complete your listing:
 
-## Project Submission
+### Step 1 — Describe your project
+
+Fill in your wallet's basic details:
 
-- Once you've filled the applicable fields, click the "Submit" button to submit your project for review. Alternatively, you can save your changes and submit later. Additional information will be visible in the modal that appears after clicking the "Submit" button.
+- **Name** — This will appear in WalletGuide and other SDKs using the WalletConnect API
+- **Link** — The homepage URL of your project
+- **Description** — A short description of your wallet
+- **Logo** — Upload your wallet's logo
+
+Click **"Continue"** to proceed.
 
   <Frame>
     <img src="/images/cloud/5.png" />
   </Frame>
 
+### Step 2 — Add wallet types
+
+Select the wallet types that apply to your project and provide the required links for each:
+
+- Mobile Wallet
+- Desktop Wallet
+- Web Wallet
+- Browser Extension
+
+Click **"+ Add"** next to each applicable type to add its details. Click **"Continue"** when done.
+
+  <Frame>
+    <img src="/images/cloud/6.png" />
+  </Frame>
+
+  <Frame>
+    <img src="/images/cloud/7.png" />
+  </Frame>
+
+### Step 3 — Add chains
+
+Select all chains your project supports. You can search by name or browse by ecosystem (EVM, Solana, Cosmos, etc.). Toggle **"My wallet supports custom chains"** if applicable.
+
+Click **"Continue"** when done.
+
+  <Frame>
+    <img src="/images/cloud/8.png" />
+  </Frame>
+
+### Step 4 — Submit your listing
+
+Add **Test instructions** to help the review team validate your WalletConnect integration. Clear test instructions help accelerate the review process.
+
+Click **"Submit"** to send your listing for review.
+
+  <Frame>
+    <img src="/images/cloud/9.png" />
+  </Frame>
+
+## Review Timeline
+
+After submitting, your listing will go through a QA review to verify your WalletConnect integration is working correctly.
+
+- **Initial review** takes **7–10 business days** on average. You can track the status in the **WalletGuide** tab of your project — it will show as **"In Review"** while pending.
+- **Once approved**, changes take approximately **24 hours** to go live on the production WalletGuide page.
+
+If your submission is not accepted, the reason will be noted in the WalletGuide tab and in the notification email. You can make the necessary changes and resubmit at any time.
+
 ## How do we test wallets?
 
 In order to offer a great user experience in our APIs and SDKs every Cloud submission goes through a QA process to make sure that the integration of the WalletConnect protocol is working correctly.
@@ -133,7 +172,12 @@ Without the correct RDNS value, your wallet may not be discoverable.
 
 ## What's Next?
 
-Now depending on whether or not your submission met all parameters, you will receive an email from the Reown team with the status of your submission. This change will also be reflected with more directions in the "Explorer" tab of your project.
-If your submission was not accepted, you can make the necessary changes and resubmit your project for review. The reason for rejection will be mentioned in the email and in the "Explorer" tab of your project.
+Now depending on whether or not your submission met all parameters, you will receive an email from the WalletConnect team with the status of your submission. The **WalletGuide** tab of your project will also reflect the current status.
+
+  <Frame>
+    <img src="/images/cloud/11.png" />
+  </Frame>
+
+If your submission was not accepted, you can make the necessary changes and resubmit your project for review. The reason for rejection will be mentioned in the email and in the WalletGuide tab of your project.
 
 In case of any questions, feel free to ask on [Github Discussions](https://github.com/orgs/WalletConnect/discussions/categories/explorer-support)