[Docs] Project Rebrand (#7455)

CORE-0000

<!-- start pr-codex -->

---

## PR-Codex overview
This PR focuses on renaming and rebranding various components and documentation from `Universal Bridge` and `Engine` to `Payments` and `Transactions`, respectively, to better reflect their functionality and purpose.

### Detailed summary
- Renamed `Universal Bridge` to `Payments` across multiple files.
- Renamed `Engine` to `Transactions` across various components and documentation.
- Updated metadata and titles in numerous `.mdx` files to reflect the new branding.
- Changed references in UI components and layout files to match new naming conventions.
- Adjusted descriptions and summaries in documentation to align with the new terms.
- Updated links and API references to point to the correct services.

> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`

<!-- end pr-codex -->

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit

* **New Features**
  * Expanded the learning resources section with updated and additional cards, including new topics like "Contracts" and "Vault".

* **Style**
  * Updated navigation and sidebar labels for improved clarity (e.g., "Connect" to "Wallets", "Bridge" to "Payments", "Engine" to "Transactions").
  * Swapped the order of the GitHub icon and theme switcher in the header for better usability.

* **Documentation**
  * Renamed all references from "Universal Bridge" to "Payments" and from "Engine" to "Transactions" across guides, FAQs, and documentation.
  * Updated instructions, headings, and content to reflect new product names and improved clarity.
  * Added a new FAQ entry explaining the difference between "Transactions Cloud" and "Dedicated" infrastructure.
  * Updated links and navigation paths to match new terminology.
  * Adjusted terminology in wallet-related documentation to replace "Connect" with "Wallets".
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Author: saminacodes

apps/portal/src/app/Header.tsx

@@ -33,15 +33,15 @@ import { ThirdwebIcon } from "../icons/thirdweb";
 const links = [
   {
     href: "/connect",
-    name: "Connect",
+    name: "Wallets",
   },
   {
     href: "/pay",
-    name: "Bridge",
+    name: "Payments",
   },
   {
     href: "/engine",
-    name: "Engine",
+    name: "Transactions",
   },
   {
     href: "/contracts",
@@ -181,7 +181,7 @@ const sdkLinks = [
 const supportLinks = [
   {
     href: "/knowledge-base",
-    name: "Get thirdweb support",
+    name: "Articles",
   },
   {
     href: "/account",
@@ -216,6 +216,20 @@ export function Header() {
         </div>
 
         <div className="flex items-center gap-3">
+          <div className="hidden xl:block">
+            <Link
+              className="text-foreground"
+              href="https://github.com/thirdweb-dev"
+              target="_blank"
+            >
+              <GithubIcon className="mx-3 size-6" />
+            </Link>
+          </div>
+
+          <div className="hidden xl:block">
+            <ThemeSwitcher className="border-none bg-transparent" />
+          </div>
+
           <div className="hidden xl:block">
             <DocSearch variant="search" />
           </div>
@@ -231,20 +245,6 @@ export function Header() {
             </Button>
           </div>
 
-          <div className="hidden xl:block">
-            <ThemeSwitcher className="border-none bg-transparent" />
-          </div>
-
-          <div className="hidden xl:block">
-            <Link
-              className="text-foreground"
-              href="https://github.com/thirdweb-dev"
-              target="_blank"
-            >
-              <GithubIcon className="mx-3 size-6" />
-            </Link>
-          </div>
-
           <div className="flex items-center gap-1 xl:hidden">
             <ThemeSwitcher className="border-none bg-transparent" />
             <DocSearch variant="icon" />

apps/portal/src/app/connect/layout.tsx

@@ -9,7 +9,7 @@ export default async function Layout(props: { children: React.ReactNode }) {
       sideBar={sidebar}
       sidebarHeader={
         <div className="flex-col items-center gap-1">
-          <p className="py-5 font-semibold text-foreground text-lg">Connect</p>
+          <p className="py-5 font-semibold text-foreground text-lg">Wallets</p>
           <PlatformSelector selected="Overview" />
         </div>
       }

apps/portal/src/app/connect/page.mdx

@@ -34,9 +34,9 @@ export const metadata = createMetadata({
 	},
 });
 
-# What is Connect?
+# Wallets
 
-Connect is the complete toolkit for connecting every user to your application. It features customizable onboarding flows, self-custodial in-app wallets, account abstraction, onramps, and a performant API to interact with the blockchain.
+Wallets is the complete toolkit for connecting every user to your application. It features customizable onboarding flows, self-custodial in-app wallets, account abstraction, onramps, and a performant API to interact with the blockchain.
 
 ## Live Playground
 
@@ -55,7 +55,7 @@ You can interact with the React SDK in the [Live Playground](https://playground.
 
 ## Quick starts
 
-Get started with Connect in your preferred language.
+Get started with Wallets in your preferred language.
 
 <Grid>
 	<SDKCard
@@ -78,7 +78,7 @@ Get started with Connect in your preferred language.
 	/>
 </Grid>
 
-## With Connect, you can
+## With Wallets, you can
 
 - **Connect to 500+ different wallet providers** with support for every EVM network
 - **Log in and authenticate your users** with customizable and secure [email, phone, passkeys and social login](https://portal.thirdweb.com/connect/in-app-wallet/overview) flows.
@@ -90,7 +90,7 @@ Get started with Connect in your preferred language.
 <Callout variant="info" title="Have you generated a client ID?">
 	<div className="flex flex-col gap-4 items-start">
 	<p>
-		You'll need a client ID to access Connect's free blockchain APIs, storage, and more.
+		You'll need a client ID to access the Wallet APIs, storage, and more.
 	</p>
 
 	<Button asChild variant='outline'>
@@ -102,7 +102,7 @@ Get started with Connect in your preferred language.
 
 ## Supported Chains
 
-Connect is supported on every EVM compatible chain. To view the full list, visit [thirdweb chainlist](https://thirdweb.com/chainlist).
+Wallets are supported on every EVM compatible chain. To view the full list, visit [thirdweb chainlist](https://thirdweb.com/chainlist).
 
 <DocImage src={SupportedChains} />
 

apps/portal/src/app/connect/wallet/faq/page.mdx

@@ -43,7 +43,7 @@ Yes, you can easily use account abstraction with in-app wallets to enable sponso
 
 Thirdweb wallets can be used as a signer to a smart contract account (account abstraction), but it can also be used as a standalone EOA.
 
-### Is there a way to display the logged-in email address in the Connect component, similar to the wallet address?
+### Is there a way to display the logged-in email address in the Wallet component, similar to the wallet address?
 
 Yes, we show the email by default in the details modal after you connect. To display the email anywhere else using React or React Native, [check out the code snippets for all platforms](/connect/in-app-wallet/how-to/interact-with-wallets#get-the-user-email).
 

apps/portal/src/app/connect/wallet/get-started/page.mdx

@@ -40,7 +40,7 @@ Your client ID authenticates your application with thirdweb's services and provi
 
 ## Live Playground
 
-Before diving into the implementation, check out our playground to see all the various capabilities of Connect:
+Before diving into the implementation, check out our playground to see all the various capabilities of Wallets:
 
 <ArticleIconCard
     title="Try the demo"
@@ -224,7 +224,7 @@ Before diving into the implementation, check out our playground to see all the v
     }
     ```
 
-    ### Connect Button Component
+    ### Wallet Button Component
 
     Use the pre-built ConnectButton for a complete wallet connection UI:
 

apps/portal/src/app/connect/wallet/migrate-to-thirdweb/page.mdx

@@ -8,4 +8,4 @@ If you are thinking of migrating your users off another embedded wallet provider
 
 <Callout variant="info" title="Learn more">Learn more about Migration from our [GitHub repository](https://github.com/thirdweb-example/migrate)</Callout>
 
-If you’d prefer to use your existing solutions for now and take advantage of thirdweb for other parts of your application, we recommend using the [Connect SDK adapters](/typescript/v5/adapters). 
+If you’d prefer to use your existing solutions for now and take advantage of thirdweb for other parts of your application, we recommend using the [Wallet SDK adapters](/typescript/v5/adapters). 

apps/portal/src/app/engine/v2/sidebar.tsx

@@ -163,5 +163,5 @@ export const sidebar: SideBar = {
       name: "FAQ",
     },
   ],
-  name: "Engine",
+  name: "Transactions",
 };

apps/portal/src/app/engine/v3/configure-wallets/smart-server-wallet/server-wallets/page.mdx renamed to apps/portal/src/app/engine/v3/configure-wallets/server-wallets/page.mdx

@@ -4,13 +4,13 @@ Smart server wallets are smart accounts designed to perform blockchain operation
 
 ## Benefits
 
-Smart server wallets are the recommended way to perform blockchain operations with Engine.
+Smart server wallets are the recommended way to perform blockchain operations with thirdweb Transactions.
 
 - **Managed Gas Fees**: Smart server wallets manage gas fees for you by automatically paying the fees using the payment method associated with your thirdweb account. You do not have to worry about topping up 
 gas funds on your server wallets. 
 - **Secure Key Management**: Smart server wallets are secured by Vault. Read more about Vault in the Security section below.
 - **Minimal Setup:** Smart server wallets can be created with just a few clicks directly in the thirdweb dashboard. No need to manage private keys or seed phrases or secure with external key management systems.
-- **Higher Throughput:** Smart server wallets can handle higher throughput by using multi-dimensional nonces. While Engine handles concurrent transactions through a queue system, smart wallets use parallelization to process multiple transactions at the same time, more efficiently than EOAs.
+- **Higher Throughput:** Smart server wallets can handle higher throughput by using multi-dimensional nonces. While thirdweb Transactions handles concurrent transactions through a queue system, smart wallets use parallelization to process multiple transactions at the same time, more efficiently than EOAs.
 
 ## Security
 
@@ -22,4 +22,3 @@ Keys used to manage server wallets including the admin key and access keys can b
 
 Smart server wallets cost a gas premium fee for each transaction completed on any mainnet as part of account abstraction fees. There are no gas charges for testnets. 
 [See pricing page for details](https://thirdweb.com/pricing).
-

apps/portal/src/app/engine/v3/configure-wallets/smart-server-wallet/page.mdx

@@ -1,20 +1,28 @@
 import { Callout, Details } from "@doc";
 
-# Engine FAQs
+# Transactions FAQs
 
-<Details summary="How is pricing calculated for Engine Cloud?">
-Pricing is calculated through the number of write requests (ex: /v1/write/contract) and sign requests (ex: /v1/sign/transaction) made through the Engine API. For requests costs, [see the thirdweb pricing page](https://thirdweb.com/pricing). Read requests made through Engine API are free, within the RPC limits/plan. 
+<Details summary="How is pricing calculated?">
+Pricing is calculated through the number of write requests (ex: /v1/write/contract) and sign requests (ex: /v1/sign/transaction) made through the Transactions API. For requests costs, [see the thirdweb pricing page](https://thirdweb.com/pricing). Read requests made through Transactions API are free, within the RPC limits/plan. 
 
-For transactions through server wallets paid through the user's thirdweb account, users will pay a 5% premium on the gas fee of each transaction completed on any mainnet as part of account abstraction fees. There are no gas charges for testnets.
+For requests through server wallets paid through the user's thirdweb account, users will pay a 5% premium on the gas fee of each request completed on any mainnet as part of account abstraction fees. There are no gas charges for testnets.
 
 **Please note: Legacy pricing plans may be subject to the 10% fee specified when signed up instead of 5%. [See pricing page for updated plans and benefits](https://thirdweb.com/pricing)** 
 
 The breakdown for usage and transaction fees can be found in your usage dashboard under the team overview. 
 </Details>
 
-<Details summary="Which chains does Engine Cloud support?">
-While in beta, Engine Cloud currently supports every non ZK EVM-compatible chain which includes support for Account Abstraction. See the current list of supported chains. 
+<Details summary="Which chains does Transactions Cloud support?">
+While in beta, Transactions Cloud currently supports every non ZK EVM-compatible chain which includes support for Account Abstraction. See the current list of supported chains. 
 
 If your chain is not listed, please [contact us](https://thirdweb.com/contact-us) to prioritize enabling support. 
 </Details>
 
+<Details summary="What is the difference between Transactions Cloud and Dedicated?">
+Cloud uses shared infrastructure that allows you to get started quickly with Transactions. It is ideal for most use cases and is the recommended way to use Transactions.
+
+Dedicated is a self-hosted version of Transactions that allows you to run Transactions on your own infrastructure. 
+
+It is ideal for high throughput applications, or applications that require complete control over their infrastructure.
+</Details>
+