Merge pull request #1125 from Web3Auth/images-update

Update images and links

Author: shahbaz17

docs/README.mdx

@@ -24,6 +24,7 @@ import SEO from "@site/src/components/SEO";
 #### Effortless Social Logins, Beautiful UX, and Secure Onboarding for Web3
 
 <ProductCards />
+<IntegrationBuilderBanner />
 
 ## Resources
 

docs/authentication/social-logins/discord.mdx

@@ -23,13 +23,13 @@ To integrate Discord with Web3Auth, developers must first create a Discord App v
 
    - https://auth.web3auth.io/auth
 
-   ![Discord OAuth2.0 App Dashboard](/guides/social-providers/discord/discord-redirect-uri.png)
+   ![Discord OAuth2.0 App Dashboard](/images/authentication/discord/discord-redirect-uri.png)
 
 3. Don't forget to save your changes!
 
 4. Next, obtain the **"Client ID"** from here. We will use this in our Web3Auth Dashboard.
 
-   ![Discord OAuth2.0 App Client ID and Secret](/guides/social-providers/discord/discord-clientid-secret.png)
+   ![Discord OAuth2.0 App Client ID and Secret](/images/authentication/discord/discord-clientid-secret.png)
 
 ## Create a Discord Connection
 

docs/authentication/social-logins/facebook.mdx

@@ -20,22 +20,22 @@ To integrate Facebook with Web3Auth, developers must first create a Facebook App
 1. Follow Facebook's instructions to
    [create a new app](https://developers.facebook.com/docs/development/create-an-app).
 2. When creating an app, make sure to select `Consumer` from this screen to use Facebook Login.
-   ![Facebook OAuth2.0 App Dashboard](/guides/social-providers/facebook/facebook-app.png)
+   ![Facebook OAuth2.0 App Dashboard](/images/authentication/facebook/facebook-app.png)
 
 3. On the next screen, you'll be presented with different products you can integrate into your
    Facebook app. Click **"Set Up"** in the card representing the **Facebook Login** capability.
 
-   ![Facebook OAuth2.0 App Dashboard](/guides/social-providers/facebook/facebook-login-setup.png)
+   ![Facebook OAuth2.0 App Dashboard](/images/authentication/facebook/facebook-login-setup.png)
 
 4. Paste the following as a redirect URI into the "Valid OAuth Redirect URIs" field.
 
    - https://auth.web3auth.io/auth
 
-   ![Facebook OAuth2.0 App Dashboard](/guides/social-providers/facebook/facebook-login-settings-oauth.png)
+   ![Facebook OAuth2.0 App Dashboard](/images/authentication/facebook/facebook-login-settings-oauth.png)
 
 5. Obtain the "App ID" and "App Secret" from the **Settings > Basic** screen.
 
-   ![Facebook OAuth2.0 App Dashboard](/guides/social-providers/facebook/facebook-app-id-secret.png)
+   ![Facebook OAuth2.0 App Dashboard](/images/authentication/facebook/facebook-app-id-secret.png)
 
 ## Create a Facebook Connection
 

docs/authentication/social-logins/google.mdx

@@ -27,7 +27,7 @@ ID in the Google Cloud Console.
 
    - `https://auth.web3auth.io/auth`
 
-   ![Google OAuth2.0 App Dashboard](/guides/social-providers/google/google-app-redirect-uri.png)
+   ![Google OAuth2.0 App Dashboard](/images/authentication/google/google-app-redirect-uri.png)
 
 3. Obtain the OAuth `Client ID` from the
    [App on the Google Developer dashboard](https://console.developers.google.com/)

docs/authentication/social-logins/twitch.mdx

@@ -23,15 +23,15 @@ To integrate Twitch with Web3Auth, developers must first create a Twitch App via
 
    - [https://auth.web3auth.io/auth](https://auth.web3auth.io/auth)
 
-   ![Twitch OAuth2.0 App Dashboard](/guides/social-providers/twitch/twitch-app.png)
+   ![Twitch OAuth2.0 App Dashboard](/images/authentication/twitch/twitch-app.png)
 
 3. After creation of your Twitch app, click **Manage**
 
-   ![Twitch OAuth2.0 App Manage](/guides/social-providers/twitch/twitch-manage.png)
+   ![Twitch OAuth2.0 App Manage](/images/authentication/twitch/twitch-manage.png)
 
 4. Obtain the **Client ID**
 
-   ![Twitch OAuth2.0 App Manage](/guides/social-providers/twitch/twitch-client-id.png)
+   ![Twitch OAuth2.0 App Manage](/images/authentication/twitch/twitch-client-id.png)
 
 ## Create a Twitch Connection
 

docs/change-of-ownership.mdx

@@ -0,0 +1,23 @@
+---
+title: Change of Ownership
+sidebar_label: Change of Ownership
+description: "Change of Ownership | Documentation - Web3Auth"
+image: "images/docs-meta-cards/documentation-card.png"
+---
+
+This notice is to inform you that **Torus Labs Private Limited (Web3Auth)** has been acquired by
+**Consensys Software Inc.**
+
+Your use of the Web3Auth offerings will be subject to
+[Consensys’ Terms of Use](https://consensys.io/terms-of-use) and the processing of your data
+(including the transfer of data to Consensys) will be completed in accordance with
+[Consensys’ Privacy Notice](https://consensys.io/privacy-notice). We remain committed to protecting
+your personal information and ensuring transparency throughout this process.
+
+If you have any concerns or wish to exercise your privacy rights (e.g., data access, deletion),
+please contact us at [email protected].
+
+This update will take effect on **2 June 2025**. By continuing to use the Web3Auth offerings after
+this date, you agree and accept [Consensys’ Terms of Use](https://consensys.io/terms-of-use) and
+acknowledge that your personal data will be processed in accordance with
+[Consensys’ Privacy Notice](https://consensys.io/privacy-notice).

docs/contribute/bug-bounty.mdx

@@ -22,7 +22,7 @@ Users can choose from various authentication methods including device-based shar
 backup seed phrases, password factors, passkeys, and authenticator apps. These options offer
 flexibility for both account security and cross-device accessibility.
 
-![Backup MFA Options](/images/mfa-options.gif)
+![Backup MFA Options](/images/mfa/mfa-options.gif)
 
 ## MFA Levels
 
@@ -46,7 +46,7 @@ The `mfaSettings` parameter provides granular control over which backup factors
 users and the order in which they appear in the UI. This enables developers to tailor the MFA
 experience to match their application's security requirements and user preferences.
 
-![MFA Factors](/images/mfa-factors.png)
+![MFA Factors](/images/mfa/mfa-factors.png)
 
 | MFA Type                         | Ease of Access | Setup Custodiality                                                                      |
 | -------------------------------- | -------------- | --------------------------------------------------------------------------------------- |

docs/contribute/contribute.mdx

@@ -6,8 +6,8 @@ description: "Multi-Party Computation | Documentation - Web3Auth"
 
 import CommonQuestions from "@site/src/components/CommonQuestions";
 
-import KeyManagementDark from "@site/static/images/key-management-dark.png";
-import KeyManagementLight from "@site/static/images/key-management-light.png";
+import KeyManagementDark from "@site/static/images/flow-diagrams/key-management-dark.png";
+import KeyManagementLight from "@site/static/images/flow-diagrams/key-management-light.png";
 import { mpccorekit } from "@site/src/components/SDKReferenceCards";
 
 Multi-Party Computation (MPC) forms the backbone of Web3Auth's advanced wallet infrastructure,
@@ -40,8 +40,8 @@ read through [How Web3Auth Works](/how-web3auth-works) and
 
 In this setup, users are equipped with three factors for authentication and recovery:
 
-1. **OAuth Login Factor:** Managed across Web3Auth's Auth Network, accessible via OAuth providers
-   like Google.
+1. **OAuth Login Factor:** Managed across Web3Auth Network, accessible via OAuth providers like
+   Google.
 2. **Device Factor:** Stored securely on the user's device, often protected by device-specific
    security features such as biometrics.
 3. **Backup/ 2FA Factor:** Acts as a recovery share, stored separately or based on user's input with
@@ -79,7 +79,7 @@ Users employ OAuth logins, trusted devices, and other factors to manage their cr
 pairs. Importantly, the complete private keys are not stored anywhere within the Wallet
 Infrastructure system, including our databases or any participating nodes.
 
-To create a social login share, users interact with the Web3Auth Auth Network, where key generation
+To create a social login share, users interact with the Web3Auth Network, where key generation
 operates via a 5/9 consensus system. This setup guarantees that wallets remain non-custodial,
 ensuring that neither Web3Auth, Social Login Providers, nor any other party holding a key share can
 claim full ownership.