diff --git a/content/pages/_partials/_web-analytics-setup.md b/content/pages/_partials/_web-analytics-setup.md
index c51f105d39d..7aa4ee546b6 100644
--- a/content/pages/_partials/_web-analytics-setup.md
+++ b/content/pages/_partials/_web-analytics-setup.md
@@ -6,7 +6,7 @@ _build:
 ---
 
 1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/login).
-2. From Account Home, select **Pages**.
+2. From Account Home, select **Workers & Pages**.
 3. Select your Pages project.
 4. Go to **Settings** > **General** > and select **Enable Web Analytics**. 
 
diff --git a/content/pages/framework-guides/deploy-a-blazor-site.md b/content/pages/framework-guides/deploy-a-blazor-site.md
index d85ab325d77..90a58a53fca 100644
--- a/content/pages/framework-guides/deploy-a-blazor-site.md
+++ b/content/pages/framework-guides/deploy-a-blazor-site.md
@@ -44,7 +44,12 @@ $ dotnet new gitignore
 
 ## Deploying with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** dashboard and selecting **Create a project**. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
+
+Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
 
 <div>
 
diff --git a/content/pages/framework-guides/deploy-a-brunch-site.md b/content/pages/framework-guides/deploy-a-brunch-site.md
index 325f787c7d0..892b194afb1 100644
--- a/content/pages/framework-guides/deploy-a-brunch-site.md
+++ b/content/pages/framework-guides/deploy-a-brunch-site.md
@@ -29,10 +29,10 @@ $ brunch new proj -s es6
 
 ## Deploy with Cloudflare Pages
 
-Deploy your site to Pages:
+To deploy your site to Pages:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/).
-2. In **Account Home**, select **Pages** > **Create a project**. 
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
 3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, select *Brunch* as your **Framework preset**. Your selection will provide the following information.
 
 {{<table-wrap>}}
diff --git a/content/pages/framework-guides/deploy-a-docusaurus-site.md b/content/pages/framework-guides/deploy-a-docusaurus-site.md
index fb03e57c28e..6a2c8bc3de3 100644
--- a/content/pages/framework-guides/deploy-a-docusaurus-site.md
+++ b/content/pages/framework-guides/deploy-a-docusaurus-site.md
@@ -21,10 +21,10 @@ $ npx create-docusaurus@latest my-website classic
 
 ## Deploy with Cloudflare Pages
 
-Deploy your site to Pages:
+To deploy your site to Pages:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/).
-2. In **Account Home**, select **Pages** > **Create a project**. 
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
 3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, select *Docusaurus* as your **Framework preset**. Your selection will provide the following information.
 
 {{<table-wrap>}}
diff --git a/content/pages/framework-guides/deploy-a-gatsby-site.md b/content/pages/framework-guides/deploy-a-gatsby-site.md
index 9b47c785ecf..08d6b02f1f0 100644
--- a/content/pages/framework-guides/deploy-a-gatsby-site.md
+++ b/content/pages/framework-guides/deploy-a-gatsby-site.md
@@ -29,7 +29,11 @@ $ gatsby new my-gatsby-site https://github.com/alxshelepenok/gatsby-starter-lume
 
 ## Deploying with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
+3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
 
 <div>
 
diff --git a/content/pages/framework-guides/deploy-a-gridsome-site.md b/content/pages/framework-guides/deploy-a-gridsome-site.md
index 074b26aece5..9a40ad6cbfb 100644
--- a/content/pages/framework-guides/deploy-a-gridsome-site.md
+++ b/content/pages/framework-guides/deploy-a-gridsome-site.md
@@ -29,7 +29,11 @@ $ gridsome create my-gridsome-website
 
 ## Deploy with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** dashboard and selecting **Create a project**. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, the following information will be provided:
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
+3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, the following information will be provided:
 
 <div>
 
diff --git a/content/pages/framework-guides/deploy-a-hexo-site.md b/content/pages/framework-guides/deploy-a-hexo-site.md
index 8a168a8204d..3792a379a85 100644
--- a/content/pages/framework-guides/deploy-a-hexo-site.md
+++ b/content/pages/framework-guides/deploy-a-hexo-site.md
@@ -53,7 +53,11 @@ Inside of `hello-hexo.md`, use Markdown to write the content of the article. You
 
 ## Deploying with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
+3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
 
 <div>
 
@@ -80,7 +84,7 @@ Every time you commit new code to your Hexo site, Cloudflare Pages will automati
 
 Some Hexo themes or plugins have additional requirements for different Node.js versions. To use a specific Node.js version for Hexo:
 
-1. Go to **your Pages project**.
+1. Go to your Pages project.
 2. Go to **Settings** > **Environment variables**.
 3. Set the environment variable `NODE_VERSION` and a value of your required Node.js version (for example, `14.3`).
 
diff --git a/content/pages/framework-guides/deploy-a-hono-site.md b/content/pages/framework-guides/deploy-a-hono-site.md
index 35eb26c0767..55a4245896f 100644
--- a/content/pages/framework-guides/deploy-a-hono-site.md
+++ b/content/pages/framework-guides/deploy-a-hono-site.md
@@ -116,7 +116,11 @@ You should be able to review your generated web application at `http://localhost
 
 ## Deploy with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
+3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
 
 <div>
 
diff --git a/content/pages/framework-guides/deploy-a-hugo-site.md b/content/pages/framework-guides/deploy-a-hugo-site.md
index 641d5501d56..1773c70f1d2 100644
--- a/content/pages/framework-guides/deploy-a-hugo-site.md
+++ b/content/pages/framework-guides/deploy-a-hugo-site.md
@@ -165,7 +165,11 @@ Inside of `hello-world.md`, add some initial content to create your post. Remove
 
 ## Deploy with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
+3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
 
 <div>
 
diff --git a/content/pages/framework-guides/deploy-a-jekyll-site.md b/content/pages/framework-guides/deploy-a-jekyll-site.md
index 5d00e85c652..be0822c3356 100644
--- a/content/pages/framework-guides/deploy-a-jekyll-site.md
+++ b/content/pages/framework-guides/deploy-a-jekyll-site.md
@@ -62,7 +62,11 @@ If you are migrating an existing Jekyll project to Pages, confirm that your `Gem
 
 ## Deploying with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
+3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
 
 <div>
 
diff --git a/content/pages/framework-guides/deploy-a-nextjs-site.md b/content/pages/framework-guides/deploy-a-nextjs-site.md
index f3d5060ddaf..af8da8e1ae4 100644
--- a/content/pages/framework-guides/deploy-a-nextjs-site.md
+++ b/content/pages/framework-guides/deploy-a-nextjs-site.md
@@ -107,10 +107,10 @@ Refer to [Next.js' documentation about the Edge Runtime](https://nextjs.org/docs
 
 ### Deploy with Cloudflare Pages
 
-Deploy your site to Pages:
+To deploy your site to Pages:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/).
-2. In **Account Home**, select **Pages** > **Create a project**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
 3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, select _Next.js_ as your **Framework preset**. Your selection will provide the following information.
 
    {{<table-wrap>}}
@@ -149,10 +149,10 @@ After creating your project, a new `my-app` directory will be generated using th
 
 ### Deploy with Cloudflare Pages
 
-Deploy your site to Pages:
+To deploy your site to Pages:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/).
-2. In **Account Home**, select **Pages** > **Create a project**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
 3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, select _Next.js (Static HTML Export)_ as your **Framework preset**. Your selection will provide the following information.
 
    {{<table-wrap>}}
diff --git a/content/pages/framework-guides/deploy-a-nuxt-site.md b/content/pages/framework-guides/deploy-a-nuxt-site.md
index caa2bfcf82d..333ad3bb952 100644
--- a/content/pages/framework-guides/deploy-a-nuxt-site.md
+++ b/content/pages/framework-guides/deploy-a-nuxt-site.md
@@ -31,7 +31,10 @@ $ npm run dev
 
 ## Deploying with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**.
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
 
 You will be asked to authorize access to your GitHub account if you have not already done so. Cloudflare needs this so that it can monitor and deploy your projects from the source. You may narrow access to specific repositories if you prefer; however, you will have to manually update this list [within your GitHub settings](https://github.com/settings/installations) when you want to add more repositories to Cloudflare Pages.
 
diff --git a/content/pages/framework-guides/deploy-a-pelican-site.md b/content/pages/framework-guides/deploy-a-pelican-site.md
index 3ba99f92d86..42088f7317d 100644
--- a/content/pages/framework-guides/deploy-a-pelican-site.md
+++ b/content/pages/framework-guides/deploy-a-pelican-site.md
@@ -35,10 +35,10 @@ This is the directory name that you will set in the build command.
 
 ## Deploy with Cloudflare Pages
 
-Deploy your site to Pages:
+To deploy your site to Pages:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/).
-2. In **Account Home**, select **Pages** > **Create a project**. 
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
 3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, select *Pelican* as your **Framework preset**. Your selection will provide the following information. The build command `pelican content` refers to the `content` folder you made earlier in this guide.
 
 {{<table-wrap>}}
diff --git a/content/pages/framework-guides/deploy-a-preact-site.md b/content/pages/framework-guides/deploy-a-preact-site.md
index 7f77e6b5a3d..334e77ffd6e 100644
--- a/content/pages/framework-guides/deploy-a-preact-site.md
+++ b/content/pages/framework-guides/deploy-a-preact-site.md
@@ -25,7 +25,10 @@ $ cd your-project-name
 
 ## Deploying with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**.
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
 
 You will be asked to authorize access to your GitHub account if you have not already done so. Cloudflare needs this so that it can monitor and deploy your projects from the source. You may narrow access to specific repositories if you prefer; however, you will have to manually update this list [within your GitHub settings](https://github.com/settings/installations) when you want to add more repositories to Cloudflare Pages.
 
diff --git a/content/pages/framework-guides/deploy-a-qwik-site.md b/content/pages/framework-guides/deploy-a-qwik-site.md
index 72cf292b6ec..a35d937501c 100644
--- a/content/pages/framework-guides/deploy-a-qwik-site.md
+++ b/content/pages/framework-guides/deploy-a-qwik-site.md
@@ -42,7 +42,11 @@ $ npm start
 
 ## Deploying with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
+3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
 
 <div>
 
diff --git a/content/pages/framework-guides/deploy-a-react-site.md b/content/pages/framework-guides/deploy-a-react-site.md
index a3e09dd87bc..23987b24cfe 100644
--- a/content/pages/framework-guides/deploy-a-react-site.md
+++ b/content/pages/framework-guides/deploy-a-react-site.md
@@ -35,7 +35,11 @@ $ npm start
 
 ## Deploying with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
+3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
 
 <div>
 
diff --git a/content/pages/framework-guides/deploy-a-remix-site.md b/content/pages/framework-guides/deploy-a-remix-site.md
index eb02fc7f4ff..de14558a4d5 100644
--- a/content/pages/framework-guides/deploy-a-remix-site.md
+++ b/content/pages/framework-guides/deploy-a-remix-site.md
@@ -40,7 +40,11 @@ $ npm run dev
 
 ## Deploying with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
+3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
 
 <div>
 
diff --git a/content/pages/framework-guides/deploy-a-solid-site.md b/content/pages/framework-guides/deploy-a-solid-site.md
index ed775376416..76d7fcb8f53 100644
--- a/content/pages/framework-guides/deploy-a-solid-site.md
+++ b/content/pages/framework-guides/deploy-a-solid-site.md
@@ -69,7 +69,11 @@ export default defineConfig({
 
 ## Deploying with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**. Select the new GitHub repository that you created and, in **Set up builds and deployments**, provide the following information:
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
+3. Select the new GitHub repository that you created and, in **Set up builds and deployments**, provide the following information:
 
 <div>
 
diff --git a/content/pages/framework-guides/deploy-a-sphinx-site.md b/content/pages/framework-guides/deploy-a-sphinx-site.md
index d352e21b3b2..599d0432deb 100644
--- a/content/pages/framework-guides/deploy-a-sphinx-site.md
+++ b/content/pages/framework-guides/deploy-a-sphinx-site.md
@@ -214,7 +214,11 @@ $ git push -u origin main
 
 ## Deploying with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
+3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
 
 <div>
 
diff --git a/content/pages/framework-guides/deploy-a-svelte-site.md b/content/pages/framework-guides/deploy-a-svelte-site.md
index 2bd974810b1..e49d4b9cfda 100644
--- a/content/pages/framework-guides/deploy-a-svelte-site.md
+++ b/content/pages/framework-guides/deploy-a-svelte-site.md
@@ -121,7 +121,10 @@ If you are using any adapter different from the default SvelteKit adapter, remem
 
 ## Deploy with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**.
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
 
 You will be asked to authorize access to your GitHub account if you have not already done so. Cloudflare needs this authorization to deploy your projects from your GitHub account. You may narrow Cloudflare's access to specific repositories. However, you will have to manually update this list [within your GitHub settings](https://github.com/settings/installations) when you want to add more repositories to Cloudflare Pages.
 
diff --git a/content/pages/framework-guides/deploy-a-vite3-project.md b/content/pages/framework-guides/deploy-a-vite3-project.md
index e877e15f76a..e9233653bdb 100644
--- a/content/pages/framework-guides/deploy-a-vite3-project.md
+++ b/content/pages/framework-guides/deploy-a-vite3-project.md
@@ -41,17 +41,17 @@ $ gh repo create
 $ git push
 ```
 
-To deploy your project with Pages:
+To deploy your site to Pages:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Go to **Pages** > **Create a project** > **Connect to git**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
 3. Select your new GitHub repository.
 4. In the **Set up builds and deployments**, set `npm run build` as the **Build command**, and `dist` as the **Build output directory**.
 5. Select **Environment variables (advanced)** > **+ Add variable** > configure a `NODE_VERSION` variable with a value of any version of Node greater than `14.18` -- this example uses `16`:
 
 After completing configuration, select **Save and Deploy**.
 
-You will see your first deploy pipeline in progress. Pages installs all dependencies and builds the project as specified. After you have deployed your project, it will be available at the `<YOUR_PROJECT_NAME>.pages.dev` subdomain. Find your project's subdomain in **Pages** > select your project > **Deployments**.
+You will see your first deploy pipeline in progress. Pages installs all dependencies and builds the project as specified. After you have deployed your project, it will be available at the `<YOUR_PROJECT_NAME>.pages.dev` subdomain. Find your project's subdomain in **Workers & Pages** > select your Pages project > **Deployments**.
 
 Cloudflare Pages will automatically rebuild your project and deploy it on every new pushed commit.
 
diff --git a/content/pages/framework-guides/deploy-a-vue-site.md b/content/pages/framework-guides/deploy-a-vue-site.md
index 82b1a6d4bc3..b402ed909f7 100644
--- a/content/pages/framework-guides/deploy-a-vue-site.md
+++ b/content/pages/framework-guides/deploy-a-vue-site.md
@@ -24,7 +24,11 @@ $ vue create my-vue-app
 
 ## Deploying with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** dashboard and selecting **Create a project**. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
+3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
 
 <div>
 
diff --git a/content/pages/framework-guides/deploy-a-vuepress-site.md b/content/pages/framework-guides/deploy-a-vuepress-site.md
index ba1657b1618..be55db74c09 100644
--- a/content/pages/framework-guides/deploy-a-vuepress-site.md
+++ b/content/pages/framework-guides/deploy-a-vuepress-site.md
@@ -27,7 +27,11 @@ Once this is done, a scaffolded documentation site will be created in the `docs`
 
 ## Deploy with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** dashboard and selecting **Create a project**. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, the following information will be provided:
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
+3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, the following information will be provided:
 
 <div>
 
diff --git a/content/pages/framework-guides/deploy-a-zola-site.md b/content/pages/framework-guides/deploy-a-zola-site.md
index 247b77c67d3..2ba0cf9b8e8 100644
--- a/content/pages/framework-guides/deploy-a-zola-site.md
+++ b/content/pages/framework-guides/deploy-a-zola-site.md
@@ -76,7 +76,11 @@ Upon running `zola init`, you will prompted with three questions:
 
 ## Deploying with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
+3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
 
 <div>
 
diff --git a/content/pages/framework-guides/deploy-an-angular-site.md b/content/pages/framework-guides/deploy-an-angular-site.md
index 484eb2652aa..a6bdaa3d01a 100644
--- a/content/pages/framework-guides/deploy-an-angular-site.md
+++ b/content/pages/framework-guides/deploy-an-angular-site.md
@@ -43,7 +43,10 @@ With both approaches, the Angular CLI will prompt you for customization choices.
 
 ## Deploying with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**.
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
 
 You will be asked to authorize access to your GitHub account if you have not already done so. Cloudflare needs this so that it can monitor and deploy your projects from the source. You may narrow access to specific repositories if you prefer; however, you will have to manually update this list [within your GitHub settings](https://github.com/settings/installations) when you want to add more repositories to Cloudflare Pages.
 
diff --git a/content/pages/framework-guides/deploy-an-astro-site.md b/content/pages/framework-guides/deploy-an-astro-site.md
index 7d51e137731..1f06a45e4f2 100644
--- a/content/pages/framework-guides/deploy-an-astro-site.md
+++ b/content/pages/framework-guides/deploy-an-astro-site.md
@@ -44,7 +44,10 @@ $ npm run astro add cloudflare
 
 ## Deploying with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**.
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
 
 You will be asked to authorize access to your GitHub account if you have not already done so. Cloudflare needs this so that it can monitor and deploy your projects from the source. You may narrow access to specific repositories if you prefer; however, you will have to manually update this list [within your GitHub settings](https://github.com/settings/installations) when you want to add more repositories to Cloudflare Pages.
 
diff --git a/content/pages/framework-guides/deploy-an-elderjs-site.md b/content/pages/framework-guides/deploy-an-elderjs-site.md
index 162d4cd0ec3..a31d8b6f2a8 100644
--- a/content/pages/framework-guides/deploy-an-elderjs-site.md
+++ b/content/pages/framework-guides/deploy-an-elderjs-site.md
@@ -26,7 +26,10 @@ The Elder.js template includes a number of pages and examples showing how to bui
 
 ## Deploying with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**.
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
 
 You will be asked to authorize access to your GitHub account if you have not already done so. Cloudflare needs this so that it can monitor and deploy your projects from the source. You may narrow access to specific repositories if you prefer; however, you will have to manually update this list [within your GitHub settings](https://github.com/settings/installations) when you want to add more repositories to Cloudflare Pages.
 
diff --git a/content/pages/framework-guides/deploy-an-eleventy-site.md b/content/pages/framework-guides/deploy-an-eleventy-site.md
index 21283876800..b6dabf8b181 100644
--- a/content/pages/framework-guides/deploy-an-eleventy-site.md
+++ b/content/pages/framework-guides/deploy-an-eleventy-site.md
@@ -39,7 +39,11 @@ $ git push -u origin main
 
 ## Deploying with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**. Select the new GitHub repository that you created and choose "Eleventy" from the Framework preset dropdown.
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
+3. Select the new GitHub repository that you created and choose _Eleventy_ from the Framework preset dropdown.
 
 {{<Aside type="note">}}
 
diff --git a/content/pages/framework-guides/deploy-an-emberjs-site.md b/content/pages/framework-guides/deploy-an-emberjs-site.md
index 8182a887ee3..a188cf8e69e 100644
--- a/content/pages/framework-guides/deploy-an-emberjs-site.md
+++ b/content/pages/framework-guides/deploy-an-emberjs-site.md
@@ -36,10 +36,10 @@ $ npm start
 
 ## Deploy with Cloudflare Pages
 
-Deploy your site to Pages:
+To deploy your site to Pages:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/).
-2. In **Account Home**, select **Pages** > **Create a project**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
 3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, select _Ember_ as your **Framework preset**. Your selection will provide the following information:
 
 {{<table-wrap>}}
diff --git a/content/pages/framework-guides/deploy-an-mkdocs-site.md b/content/pages/framework-guides/deploy-an-mkdocs-site.md
index dbbcbdf8262..02ef062e68b 100644
--- a/content/pages/framework-guides/deploy-an-mkdocs-site.md
+++ b/content/pages/framework-guides/deploy-an-mkdocs-site.md
@@ -37,10 +37,10 @@ You have successfully created a GitHub repository and pushed your Mkdocs project
 
 ## Deploy with Cloudflare Pages
 
-Deploy your site to Pages:
+To deploy your site to Pages:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/).
-2. In **Account Home**, select **Pages** > **Create a project**. 
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
 3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, select *Mkdocs* as your **Framework preset**. Your selection will provide the following information:
 
 {{<table-wrap>}}
diff --git a/content/pages/framework-guides/deploy-anything.md b/content/pages/framework-guides/deploy-anything.md
index 37c50ea5957..9e779c11992 100644
--- a/content/pages/framework-guides/deploy-anything.md
+++ b/content/pages/framework-guides/deploy-anything.md
@@ -13,7 +13,11 @@ Cloudflare supports deploying any static HTML website to Cloudflare Pages. If yo
 
 ## Deploy with Cloudflare Pages
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
+3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
 
 <div>
 
diff --git a/content/pages/get-started/index.md b/content/pages/get-started/index.md
index 87e1cc71425..38804456101 100644
--- a/content/pages/get-started/index.md
+++ b/content/pages/get-started/index.md
@@ -21,9 +21,9 @@ This guide will take you through the Git setup option.
 
 Pages offers support for [GitHub](https://github.com/) and [GitLab](https://gitlab.com/). To create your first Pages project:
 
-1. Log in to the Cloudflare dashboard.
-2. Select your account in **Account Home** > **Pages**.
-3. Select **Create a project** > **Connect to Git**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages**.
+3. Select **Create** > **Pages** > **Import from Git**.
 
 You will be prompted to sign in with your preferred Git provider. This allows Cloudflare Pages to deploy your projects, and update your PRs with [preview deployments](/pages/platform/preview-deployments/).
 
@@ -125,8 +125,8 @@ After your first deploy, select **Continue to project** to see your project's co
 To delete your Pages project:
 
 1.  Go back to the **Account Home** or use the drop-down menu at the top of the dashboard.
-2.  Select **Pages**.
-3.  Remove your project by selecting your **Pages project** > **Settings** > **Delete project**.
+2.  Select **Workers & Pages**.
+3.  Select your Pages project > **Settings** > **Delete project**.
 
 {{<Aside type="warning">}}
 
diff --git a/content/pages/how-to/build-commands-branches.md b/content/pages/how-to/build-commands-branches.md
index f53351ddb52..c61e63ceb6d 100644
--- a/content/pages/how-to/build-commands-branches.md
+++ b/content/pages/how-to/build-commands-branches.md
@@ -39,8 +39,9 @@ fi
 
 To put your changes into effect:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) > **Pages**.
-2. Go to **Settings** > **Build & deployments** > **Build configurations** > **Edit configurations**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In Account Home, select **Workers & Pages** > select your Pages project.
+3. Go to **Settings** > **Build & deployments** > **Build configurations** > **Edit configurations**.
 3. Update the **Build command** field value to `bash build.sh` and select **Save**.
 
 To test that your build is successful, deploy your project.
\ No newline at end of file
diff --git a/content/pages/how-to/custom-branch-aliases.md b/content/pages/how-to/custom-branch-aliases.md
index d3f6f143336..ce91a5ed1f3 100644
--- a/content/pages/how-to/custom-branch-aliases.md
+++ b/content/pages/how-to/custom-branch-aliases.md
@@ -26,8 +26,8 @@ Next, add a custom domain under your Pages project for your desired custom domai
 To do this:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login).
-2. In Account Home, go to **Pages**.
-3. Select your project.
+2. In Account Home, go to **Workers & Pages**.
+3. Select your Pages project.
 4. Select **Custom domains** > **Setup a custom domain**.
 5. Input the domain you would like to use, such as `staging.example.com`
 6. Select **Continue** > **Activate domain**
diff --git a/content/pages/how-to/deploy-a-wordpress-site.md b/content/pages/how-to/deploy-a-wordpress-site.md
index ee807a014a2..da6e267cbfd 100644
--- a/content/pages/how-to/deploy-a-wordpress-site.md
+++ b/content/pages/how-to/deploy-a-wordpress-site.md
@@ -40,8 +40,8 @@ In the **Activity Log**, find the **ZIP archive created** message and select **C
 
 With your ZIP file downloaded, deploy your site to Pages:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com).
-2. Go to **Pages** > **Create a project** > **Direct Upload**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Upload assets**.
 3. Name your project > **Create project**.
 4. Drag and drop your ZIP file or select it from your computer.
 5. After your files have been uploaded, select **Deploy site**.
diff --git a/content/pages/how-to/use-direct-upload-with-continuous-integration.md b/content/pages/how-to/use-direct-upload-with-continuous-integration.md
index 94e5e44281d..3be0aa57ac9 100644
--- a/content/pages/how-to/use-direct-upload-with-continuous-integration.md
+++ b/content/pages/how-to/use-direct-upload-with-continuous-integration.md
@@ -108,7 +108,7 @@ After you have generated your Cloudflare API token and found your account ID in
 
 To add environment variables, in the CircleCI web application:
 
-1. Go to your project's settings.
+1. Go to your Pages project > **Settings**.
 2. Select **Projects** in the side menu.
 3. Select the ellipsis (...) button in the project's row. You will see the option to add environment variables.
 4. Select **Environment Variables** > **Add Environment Variable**.
diff --git a/content/pages/how-to/use-worker-for-ab-testing-in-pages.md b/content/pages/how-to/use-worker-for-ab-testing-in-pages.md
index 8ee89732030..f19c2bbc7fd 100644
--- a/content/pages/how-to/use-worker-for-ab-testing-in-pages.md
+++ b/content/pages/how-to/use-worker-for-ab-testing-in-pages.md
@@ -168,4 +168,8 @@ export const onRequest = [abTest];
 
 After you have set up your `functions/_middleware.js` file in your project you are ready to deploy with Pages. Push your project changes to GitHub/GitLab.
 
-After you have deployed your application, you will see your middleware Function in the Cloudflare dashboard under **Pages** > **Settings** > **Functions** > **Configuration**. 
+After you have deployed your application, review your middleware Function:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In Account Home, select **Workers & Pages**.
+3. Select your Pages project > **Settings** > **Functions** > **Configuration**. 
diff --git a/content/pages/migrations/migrating-from-workers/index.md b/content/pages/migrations/migrating-from-workers/index.md
index 9eeaae09d65..217ec4f151d 100644
--- a/content/pages/migrations/migrating-from-workers/index.md
+++ b/content/pages/migrations/migrating-from-workers/index.md
@@ -73,6 +73,6 @@ These options allow you to create and name a new project from the CLI or dashboa
 
 ## Cleaning up your old application and assigning the domain
 
-After you have deployed your application, navigate to [Workers](https://dash.cloudflare.com/?to=/:account/workers) and remove your old Workers project by going to your **Workers project** > **Settings** > **Delete**.
+After you have deployed your application, go to [**Workers & Pages**](https://dash.cloudflare.com/?to=/:account/workers) and remove your old Workers project by going to your Worker > **Settings** > **Delete**.
 
 With your Workers application removed, requests will go to your Pages application. You have successfully migrated your Workers Sites project to Cloudflare Pages by completing this guide.
diff --git a/content/pages/migrations/migrating-jekyll-from-github-pages.md b/content/pages/migrations/migrating-jekyll-from-github-pages.md
index 973af4e6c7f..ca4dd0b0993 100644
--- a/content/pages/migrations/migrating-jekyll-from-github-pages.md
+++ b/content/pages/migrations/migrating-jekyll-from-github-pages.md
@@ -113,7 +113,11 @@ If you are configuring your Cloudflare Pages site for the first time, refer to t
 
 {{</Aside>}}
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In Account Home, select **Workers & Pages** > **Create** > **Pages** > **Import from Git**.
+3. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, provide the following information:
 
 <div>
 
diff --git a/content/pages/platform/api.md b/content/pages/platform/api.md
index adc165f22f2..4c9ffa642d9 100644
--- a/content/pages/platform/api.md
+++ b/content/pages/platform/api.md
@@ -27,7 +27,7 @@ $ curl 'https://api.cloudflare.com/client/v4/accounts/{account_id}/pages/project
   -H 'Authorization: Bearer {API_token}'
 ```
 
-Try it with one of your projects by replacing `{account_id}`, `{project_name}`, and `{API_token}`. You can find your `account_id` in the [Workers dashboard](https://dash.cloudflare.com/?to=/:account/workers).
+Try it with one of your projects by replacing `{account_id}`, `{project_name}`, and `{API_token}`. Refer to [Find your account ID](/fundamentals/get-started/basic-tasks/find-account-and-zone-ids/) for more information.
 
 ## Examples
 
diff --git a/content/pages/platform/build-configuration.md b/content/pages/platform/build-configuration.md
index 1993a92e488..524d7c55be8 100644
--- a/content/pages/platform/build-configuration.md
+++ b/content/pages/platform/build-configuration.md
@@ -69,7 +69,11 @@ If you are not using a framework, leave the **Build command** field blank.
 
 ## Environment variables
 
-If your project makes use of environment variables to build your site, you can provide custom environment variables by going to **Account Home** > **Pages** > **your Pages project** > **Settings** > **Environment variables**.
+If your project makes use of environment variables to build your site, provide custom environment variables:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In **Account Home**, select **Workers & Pages** > your Pages project.
+3. Select **Settings** > **Environment variables**.
 
 The following system environment variables are injected by default (but can be overridden):
 
diff --git a/content/pages/platform/custom-domains.md b/content/pages/platform/custom-domains.md
index 197e978d63c..d60f95e78e6 100644
--- a/content/pages/platform/custom-domains.md
+++ b/content/pages/platform/custom-domains.md
@@ -9,7 +9,7 @@ When deploying your Pages project, you may wish to point custom domains (or subd
 
 {{<Aside type="note" header="Purging the cache">}}
 
-If Page Rules or other cache settings are used on your custom domain, that may lead to stale assets being served after a new build. You can resolve this by selecting **Caching** > **Configuration** > [**Purge Everything**](/cache/how-to/purge-cache/#purge-everything) in the dashboard to ensure the latest build gets served.
+If Page Rules or other cache settings are used on your custom domain, that may lead to stale assets being served after a new build. Resolve this by selecting **Caching** > **Configuration** > [**Purge Everything**](/cache/how-to/purge-cache/#purge-everything) in the dashboard to ensure the latest build gets served.
 
 {{</Aside>}}
 
@@ -18,7 +18,7 @@ If Page Rules or other cache settings are used on your custom domain, that may l
 To add a custom domain:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login).
-2. Select your account in **Account Home** > **Pages**.
+2. Select your account in **Account Home** > **Workers & Pages**.
 3. Select your Pages project > **Custom domains**.
 4. Select **Set up a domain**.
 5. Provide the domain that you would like to serve your Cloudflare Pages site on and select **Continue**.
@@ -65,9 +65,9 @@ Then, in **DNS** > **Records**:
 2.  Select **Edit**.
 3.  Select **Delete**.
 
-Next, in the **Pages** dashboard:
+Next, in Account Home, go to **Workers & Pages**:
 
-1.  Select **your Pages project**.
+1.  Select your Pages project.
 2.  Go to **Custom domains**.
 3.  Select the **three dot icon** next to your custom domain > **Remove domain**.
 
diff --git a/content/pages/platform/debugging-pages.md b/content/pages/platform/debugging-pages.md
index 6b95077663b..9ef049ebc5b 100644
--- a/content/pages/platform/debugging-pages.md
+++ b/content/pages/platform/debugging-pages.md
@@ -12,7 +12,7 @@ When setting up your Pages project, you may encounter various errors that preven
 You can review build errors in your Pages build log. To access your build log:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com).
-2. In **Account Home**, go to **Pages**.
+2. In **Account Home**, go to **Workers & Pages**.
 3. Select your Pages project > **View build**.
 
 ![After logging in to the Cloudflare dashboard, access the build log by following the instructions above](../media/pages-build-log.png)
diff --git a/content/pages/platform/deploy-hooks.md b/content/pages/platform/deploy-hooks.md
index b27a5376112..33b181009db 100644
--- a/content/pages/platform/deploy-hooks.md
+++ b/content/pages/platform/deploy-hooks.md
@@ -13,9 +13,10 @@ With Deploy Hooks, you can trigger deployments using event sources beyond commit
 
 To create a Deploy Hook:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) > **Pages**.
-2. Select your Pages project.
-3. Go to **Settings** > **Builds & deployments** and select **Add deploy hook** to start configuration.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In Account Home, select **Workers & Pages**.
+3. Select your Pages project.
+4. Go to **Settings** > **Builds & deployments** and select **Add deploy hook** to start configuration.
 
 ![Add a deploy hook on the Cloudflare dashboard](/pages/platform/media/deploy-hooks-add.png)
 
diff --git a/content/pages/platform/direct-upload.md b/content/pages/platform/direct-upload.md
index 8bb687ce792..06956e4a89e 100644
--- a/content/pages/platform/direct-upload.md
+++ b/content/pages/platform/direct-upload.md
@@ -100,8 +100,8 @@ For step-by-step directions on how to use Wrangler and continuous integration to
 To deploy with drag and drop:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login).
-2. In **Account Home**, select your account > **Pages**.
-3. Select **Create a project** > **Direct Upload** > enter your project name in the provided field > **Create project**. 
+2. In **Account Home**, select your account > **Workers & Pages**.
+3. Select **Create** > **Pages** > **Upload assets** > enter your project name in the provided field > **Create project**. 
 
 Your project will be served from `<PROJECT_NAME>.pages.dev`. Next drag and drop your build output directory into the uploading frame. Once your files have been successfully uploaded, select **Save and Deploy** and continue to your newly deployed project. 
 
diff --git a/content/pages/platform/early-hints.md b/content/pages/platform/early-hints.md
index 6d2c2e6c87e..1719d4d78a4 100644
--- a/content/pages/platform/early-hints.md
+++ b/content/pages/platform/early-hints.md
@@ -7,8 +7,8 @@ title: Early Hints
 
 [Early Hints](/cache/about/early-hints/) help the browser to load webpages faster. Early Hints is enabled automatically on all `pages.dev` domains. [To enable](/cache/about/early-hints/#enabling-early-hints) Early Hints for your custom domains:
 
-1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain.
-2. Go to **Speed** > **Optimization**.
+1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. Select your website > **Speed** > **Optimization**.
 3. Turn on the **Early Hints** toggle.
 
 Early Hints automatically caches any [`preload`](https://developer.mozilla.org/en-US/docs/Web/HTML/Link_types/preload) and [`preconnect`](https://developer.mozilla.org/en-US/docs/Web/HTML/Link_types/preconnect) type [`Link` headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Link) to send as Early Hints to the browser. The hints are sent to the browser before the full response is prepared, and the browser can figure out how to load the webpage faster for the end user. There are two ways to create these `Link` headers in Pages:
diff --git a/content/pages/platform/functions/bindings.md b/content/pages/platform/functions/bindings.md
index 31a07e26e10..b0fed53c167 100644
--- a/content/pages/platform/functions/bindings.md
+++ b/content/pages/platform/functions/bindings.md
@@ -20,9 +20,9 @@ By default, data in local development is not persisted. This means if you write
 
 [Workers KV](/workers/wrangler/workers-kv/) is Cloudflare's key-value storage solution. To bind your KV namespace to your Pages Function:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com).
-2. In **Account Home**, select **Pages**.
-3. In your Pages project, go to **Settings** > **Functions** > **KV namespace bindings** > **Add binding**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In **Account Home**, select **Workers & Pages**.
+3. Select your Pages project > **Settings** > **Functions** > **KV namespace bindings** > **Add binding**.
 4. Choose whether you would like to set up the binding in your **Production** or **Preview** environment.
 5. Give your binding a name under **Variable name**.
 6. Under **KV namespace**, select your desired namespace. You must repeat steps 5 and 6 for both the **Production** and **Preview** environments.
@@ -61,9 +61,9 @@ While developing locally, interact with your KV namespace by adding `-k <BINDING
 
 [Durable Objects](/workers/learning/using-durable-objects/) (DO) are Cloudflare's strongly consistent data store that power capabilities such as connecting WebSockets and handling state. To bind your DO namespace to your Pages Function:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com).
-2. In **Account Home**, select **Pages**.
-3. In your Pages project, go to **Settings** > **Functions** > **Durable Object bindings** > **Add binding**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In **Account Home**, select **Workers & Pages**.
+3. Select your Pages project > **Settings** > **Functions** > **Durable Object bindings** > **Add binding**.
 4. Choose whether you would like to set up the binding in your **Production** or **Preview** environment.
 5. Give your binding a name under **Variable name**.
 6. Under **Durable Object namespace**, select your desired namespace. You must repeat steps 5 and 6 for both the **Production** and **Preview** environments.
@@ -105,9 +105,9 @@ export const onRequestGet: PagesFunction<Env> = async (context) => {
 
 [R2](/r2/) is Cloudflare's blob storage solution that allows developers to store large amounts of unstructured data without the egress fees. To bind your R2 bucket to your Pages Function:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com).
-2. In **Account Home**, select **Pages**.
-3. In your Pages project, go to **Settings** > **Functions** > **R2 bucket bindings** > **Add binding**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In **Account Home**, select **Workers & Pages**.
+3. Select your Pages project > **Settings** > **Functions** > **R2 bucket bindings** > **Add binding**.
 4. Choose whether you would like to set up the binding in your **Production** or **Preview** environment.
 5. Give your binding a name under **Variable name**.
 6. Under **R2 bucket**, select your desired R2 bucket. You must repeat steps 5 and 6 for both the **Production** and **Preview** environments.
@@ -152,9 +152,9 @@ While developing locally, interact with an R2 bucket by adding `--r2=<BINDING_NA
 
 Cloudflare [D1](/d1/) is Cloudflare's first SQL database built on SQLite. To bind your D1 database to your Pages Function:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com).
-2. In **Account Home**, select **Pages**.
-3. In your Pages project, go to **Settings** > **Functions** > **D1 database bindings** > **Add binding**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In **Account Home**, select **Workers & Pages**.
+3. Select your Pages project > **Settings** > **Functions** > **D1 database bindings** > **Add binding**.
 4. Choose whether you would like to set up the binding in your **Production** or **Preview** environment.
 5. Give your binding a name under **Variable name**.
 6. Under **D1 database**, select your desired D1 database. You must repeat steps 5 and 6 for both the **Production** and **Preview** environments.
@@ -212,9 +212,9 @@ Refer to the [D1 client API documentation](/d1/platform/client-api/) for the API
 
 [Service bindings](/workers/runtime-apis/service-bindings/) enable you to call a Worker from within your Pages Function. To add a service binding to your Pages Function:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com).
-2. In **Account Home**, select **Pages**.
-3. In your Pages project, go to **Settings** > **Functions** > **Service bindings** > **Add binding**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In **Account Home**, select **Workers & Pages**.
+3. Select your Pages project > **Settings** > **Functions** > **Service bindings** > **Add binding**.
 4. Choose whether you would like to set up the binding in your **Production** or **Preview** environment.
 5. Give your binding a name under **Variable name**.
 6. Under **Service**, select your desired Worker. You must repeat steps 5 and 6 for both the **Production** and **Preview** environments.
@@ -251,9 +251,9 @@ While developing locally, interact with a service by adding `--service=<BINDING_
 
 [Queue Producers](/queues/platform/javascript-apis/#producer) enable you to send messages into a Queue within your Pages Function. To add a Queue producer binding to your Pages Function:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com).
-2. In **Account Home**, select **Pages**.
-3. In your Pages project, go to **Settings** > **Functions** > **Queue Producers bindings** > **Add binding**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In **Account Home**, select **Workers & Pages**.
+3. Select your Pages project > **Settings** > **Functions** > **Queue Producers bindings** > **Add binding**.
 4. Choose whether you would like to set up the binding in your **Production** or **Preview** environment.
 5. Give your binding a name under **Variable name**.
 6. Under **Dataset**, input your desired dataset. You must repeat steps 5 and 6 for both the **Production** and **Preview** environments.
@@ -302,9 +302,9 @@ At this time, Wrangler does not support interacting with Queue Producers during
 
 The [Analytics Engine](/analytics/analytics-engine/) binding enables you to write analytics within your Pages Function. To add a Analytics Engine binding to your Pages Function:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com).
-2. In **Account Home**, select **Pages**.
-3. In your Pages project, go to **Settings** > **Functions** > **Analytics Engine bindings** > **Add binding**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In **Account Home**, select **Workers & Pages**.
+3. Select your Pages project > **Settings** > **Functions** > **Analytics Engine bindings** > **Add binding**.
 4. Choose whether you would like to set up the binding in your **Production** or **Preview** environment.
 5. Give your binding a name under **Variable name**.
 6. Under **Dataset**, input your desired dataset. You must repeat steps 5 and 6 for both the **Production** and **Preview** environments.
@@ -359,9 +359,9 @@ An [environment variable](/workers/platform/environment-variables/) is an inject
 
 To add Pages project environment variables:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com).
-2. In **Account Home**, select **Pages**.
-3. In your Pages project, select **Settings** > **Environment variables**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In **Account Home**, select **Workers & Pages**.
+3. Select your Pages project > **Settings** > **Environment variables**.
 4. Selecting **Add variables** under **Production** and/or **Preview**.
 6. After setting a variable name and value, select **Save**.
 
@@ -413,9 +413,9 @@ Secrets are environment variables that are encrypted and not visible once set. T
 
 To add secrets to your Pages project:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com).
-2. In **Account Home**, select **Pages**.
-3. In your Pages project, select **Settings** > **Environment variables**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In **Account Home**, select **Workers & Pages**.
+3. Select your Pages project > select **Settings** > **Environment variables**.
 4. Selecting **Add variables** under **Production** and/or **Preview**.
 5. Select **Encrypt** to create your secret.
 6. Select **Save**.
diff --git a/content/pages/platform/functions/debugging-and-logging.md b/content/pages/platform/functions/debugging-and-logging.md
index 84c9d006eef..3ac1fc8ca18 100644
--- a/content/pages/platform/functions/debugging-and-logging.md
+++ b/content/pages/platform/functions/debugging-and-logging.md
@@ -85,9 +85,9 @@ The output of each `wrangler pages deployment tail` log is a structured JSON obj
 
 To view logs for your `production` or `preview` environments associated with any deployment:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/). 
-2. In **Account Home**, select **Pages**.
-3. In your your **Pages project**, go to the deployment you want to view logs for and select **View details** > **Functions**. 
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In **Account Home**, select **Workers & Pages**.
+3. Select your Pages project, go to the deployment you want to view logs for and select **View details** > **Functions**. 
 
 Logging is available for all customers (Free, Paid, Enterprise).
 
diff --git a/content/pages/platform/functions/get-started.md b/content/pages/platform/functions/get-started.md
index bda8f432269..08d79800cf5 100644
--- a/content/pages/platform/functions/get-started.md
+++ b/content/pages/platform/functions/get-started.md
@@ -48,7 +48,7 @@ Workers runtime features, including compatibility with a subset of Node.js APIs
 Set these configurations by passing an argument to your [Wrangler](/workers/wrangler/commands/#dev-1) command or by setting them in the dashboard. To set Pages compatibility flags in the Cloudflare dashboard:
 
 1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Select **Pages** and select your Pages project.
+2. Select **Workers & Pages** and select your Pages project.
 3. Select **Settings** > **Functions** > **Compatibility Flags**.
 4. Configure your Production and Preview compatiblity flags as needed.
 
diff --git a/content/pages/platform/functions/metrics.md b/content/pages/platform/functions/metrics.md
index 5d6d931420f..59039554199 100644
--- a/content/pages/platform/functions/metrics.md
+++ b/content/pages/platform/functions/metrics.md
@@ -12,8 +12,8 @@ Functions metrics can help you diagnose issues and understand your workloads by
 
 Functions metrics aggregate request data for an individual Pages project. To view your Functions metrics:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com).
-2. In **Account Home**, select **Pages**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In **Account Home**, select **Workers & Pages**.
 3. In your Pages project, select **Functions Metrics**.
 
 There are three metrics that can help you understand the health of your Function: 
diff --git a/content/pages/platform/functions/plugins/mailchannels.md b/content/pages/platform/functions/plugins/mailchannels.md
index c7b33f39975..b00e26b2ed0 100644
--- a/content/pages/platform/functions/plugins/mailchannels.md
+++ b/content/pages/platform/functions/plugins/mailchannels.md
@@ -121,7 +121,7 @@ $ echo -n "v=DKIM1;p=" > dkim_record.txt && openssl rsa -in private_key.pem -pub
 This creates a public key from the private key (`openssl rsa -in priv_key.pem -pubout -outform der`), encodes it in base64 (`openssl base 64 -A`), and finally writes it to the `dkim_record.txt` file.
 
 
-2. Copy the contents of the `private_key.txt` file and add that as an environment variable to your Pages project by logging into the [Cloudflare dashboard](https://dash.cloudflare.com/login) > **Pages** > your Pages project > **Settings** > **Environment Variables* > **Add variables**. Set the variable name as `DKIM_PRIVATE_KEY` and the value as the contents of `private_key.txt` file.
+2. Copy the contents of the `private_key.txt` file and add that as an environment variable to your Pages project by logging into the [Cloudflare dashboard](https://dash.cloudflare.com/login) > **Workers & Pages** > your Pages project > **Settings** > **Environment Variables** > **Add variables**. Set the variable name as `DKIM_PRIVATE_KEY` and the value as the contents of `private_key.txt` file.
 
 3. Create a DNS record with the content of the generated `dkim_record.txt` file content.
 
diff --git a/content/pages/platform/functions/pricing.md b/content/pages/platform/functions/pricing.md
index deeabd902c8..961c8224564 100644
--- a/content/pages/platform/functions/pricing.md
+++ b/content/pages/platform/functions/pricing.md
@@ -12,7 +12,12 @@ Requests to your Functions are billed as Cloudflare Workers requests. Workers pl
 
 Requests to your Pages functions count towards your quota for Workers Paid plans, including requests from your Function to KV or Durable Object bindings.
 
-Pages supports both Bundled and Unbound Usage Models. When an account is first upgraded to a Paid Plan, Unbound is the default Usage Model. This default applies only to new projects created after upgrading your plan; existing projects created under the Free Plan will continue to use the Bundled Usage Model. To change the default Usage Model, go to Account Home > Pages and select Change next to the Default Usage Model in the top right of the page.
+Pages supports both Bundled and Unbound Usage Models. When an account is first upgraded to a Paid Plan, Unbound is the default Usage Model. This default applies only to new projects created after upgrading your plan; existing projects created under the Free Plan will continue to use the Bundled Usage Model. To change the default Usage Model:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In Account Home, select **Workers & Pages**.
+3. Select your Pages project.
+4. Find **Default Usage Model** on the right-side menu and select **Change**.
 
 You can update the Usage Model per project, for both Production and Preview deployments, in the Project Settings page. Like other modifications to your Project Settings, you must redeploy your site in order for this change to take effect. Requests to previous deployments will continue to be billed under the Usage Model the Function was deployed with.
 
diff --git a/content/pages/platform/known-issues.md b/content/pages/platform/known-issues.md
index b7eb59f4d91..abb93f0d5a2 100644
--- a/content/pages/platform/known-issues.md
+++ b/content/pages/platform/known-issues.md
@@ -60,7 +60,7 @@ Here are some known bugs and issues with Cloudflare Pages:
 If you would like to enable [Cloudflare Access](https://www.cloudflare.com/teams-access/)] for your preview deployments and your `*.pages.dev` domain, you must:
 
 1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/login).
-2. From Account Home, select **Pages**.
+2. From Account Home, select **Workers & Pages**.
 3. Select your Pages project.
 4. Go to **Settings** > **Enable access policy**.
 5. Select **Edit** on the Acccess policy created for your preview deployments.
diff --git a/content/pages/platform/preview-deployments.md b/content/pages/platform/preview-deployments.md
index b8fd98730b6..c2cd36c5263 100644
--- a/content/pages/platform/preview-deployments.md
+++ b/content/pages/platform/preview-deployments.md
@@ -5,7 +5,11 @@ title: Preview deployments
 
 # Preview deployments
 
-Preview deployments allow you to preview new versions of your project without deploying it to production. To view preview deployments, navigate from the **Account Home** > **Pages** and select your project.
+Preview deployments allow you to preview new versions of your project without deploying it to production. To view preview deployments:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
+2. In **Account Home**, select **Workers & Pages**.
+3. Select your project and find the deployment you would like to view.
 
 Every time you open a new pull request on your GitHub repository, Cloudflare Pages will create a unique preview URL, which will stay updated as you continue to push new commits to the branch. This is only true when pull requests originate from the repository itself.
 
@@ -36,7 +40,7 @@ By default, preview deployments are enabled and available publicly. In your proj
 To protect your preview deployments behind Cloudflare Access:
 
 1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/login).
-2. From Account Home, select **Pages**.
+2. In Account Home, select **Workers & Pages**.
 3. Select your Pages project.
 4. Go to **Settings** > **General** > and select **Enable access policy**.
 
diff --git a/content/pages/platform/redirects.md b/content/pages/platform/redirects.md
index 5b8fe3548cc..e8d68161a92 100644
--- a/content/pages/platform/redirects.md
+++ b/content/pages/platform/redirects.md
@@ -40,8 +40,8 @@ filename: _redirects
 
 In the case of some frameworks, such as Jekyll, you may need to manually copy and paste your `_redirects` file to the build output directory. To do this:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com).
-2. Go to **Pages** > your Pages project > **Settings** > **Builds & deployments**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. Go to **Workers & Pages** > your Pages project > **Settings** > **Builds & deployments**.
 3. Go to **Build configurations** > **Edit configurations** > change the build command to `jekyll build && cp _redirects _site/_redirects` and select **Save**.
 
 {{</Aside>}}
diff --git a/content/pages/tutorials/build-a-blog-using-nuxt-and-sanity/index.md b/content/pages/tutorials/build-a-blog-using-nuxt-and-sanity/index.md
index 85fdb427479..816295386e7 100644
--- a/content/pages/tutorials/build-a-blog-using-nuxt-and-sanity/index.md
+++ b/content/pages/tutorials/build-a-blog-using-nuxt-and-sanity/index.md
@@ -423,7 +423,7 @@ Publishing your project with Cloudflare Pages is an easy, two-step process: firs
 
 To push your project to GitHub, [create a new repository](https://repo.new), and follow the instructions to push your local Git repository to GitHub.
 
-After you've pushed your project to GitHub, deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, choose _Nuxt_. Pages will set the correct fields for you automatically.
+After you have pushed your project to GitHub, deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Workers & Pages** and selecting **Create** > **Pages** > **Import from Git**. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, choose _Nuxt_. Pages will set the correct fields for you automatically.
 
 When your site has been deployed, you will receive a unique URL to view it in production.
 
diff --git a/content/pages/tutorials/build-an-api-with-workers/index.md b/content/pages/tutorials/build-an-api-with-workers/index.md
index 4c5056b01fe..69081501d4d 100644
--- a/content/pages/tutorials/build-an-api-with-workers/index.md
+++ b/content/pages/tutorials/build-an-api-with-workers/index.md
@@ -405,7 +405,14 @@ Pages will deploy a new version of your site each time you publish and will set
 
 To push your project to GitHub, [create a new repository](https://repo.new), and follow the instructions to push your local Git repository to GitHub.
 
-Deploy your site to Pages by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Pages** and selecting **Create a project**. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, choose **React** -- Pages will automatically apply the correct build settings for you.
+To deploy your site to Pages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In **Account Home**, select **Workers & Pages**.
+3. Select **Create** > **Pages** > **Import from Git**.
+4. Select the new GitHub repository that you created and, in the **Set up builds and deployments** section, choose _React_.
+
+Pages will automatically apply the correct build settings for you.
 
 When your site has been deployed, you will receive a unique URL to view it in production.
 
diff --git a/content/workers/examples/images-workers.md b/content/workers/examples/images-workers.md
index 4b710388e52..344d78c5e1f 100644
--- a/content/workers/examples/images-workers.md
+++ b/content/workers/examples/images-workers.md
@@ -13,9 +13,9 @@ layout: example
 To serve images from a custom domain:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com).
-2. Select you account > select **Workers**.
-3. Select **Create a service**.
-4. In your Workers, select **Quick edit** and paste the following code.
+2. Select you account > select **Workers & Pages**.
+3. Select **Create** > **Worker** and create your Worker.
+4. In your Worker, select **Quick edit** and paste the following code.
 
 {{<tabs labels="js | ts">}}
 {{<tab label="js" default="true">}}
diff --git a/content/workers/learning/logging-workers.md b/content/workers/learning/logging-workers.md
index e2fbdd79d9d..5f568b47f3e 100644
--- a/content/workers/learning/logging-workers.md
+++ b/content/workers/learning/logging-workers.md
@@ -8,7 +8,7 @@ weight: 4
 
 You can access logs and exceptions for your Workers using the dashboard or [`wrangler tail`](/workers/wrangler/commands/#tail).
 
-The Workers platform captures all `console.log`'s and uncaught exceptions, in addition to information about the event itself. All of this can be viewed with either `wrangler tail` or on the dashboard through your **Account Home** > **Workers** > your **Workers script** > **Logs**.
+The Workers platform captures all `console.log`'s and uncaught exceptions, in addition to information about the event itself. All of this can be viewed with either `wrangler tail` or on the dashboard through your **Account Home** > **Workers & Pages** > your Workers > **Logs**.
 
 {{<Aside type="warning" header="Warning">}}
 This feature is not available for zones on the [Cloudflare China Network](/china-network/).
@@ -116,7 +116,7 @@ You can customize how `wrangler tail` works to fit your needs: refer to [the `wr
 
 ## View logs from the dashboard
 
-You can review the production logs associated with any Worker by [logging in to the Cloudflare dashboard](https://dash.cloudflare.com?to=/:account/workers/overview). From your **Account Home** > go to **Workers** > select your **Worker** > and select **Logs**. Logging is available for all customers, including those on the free plan.
+You can review the production logs associated with any Worker by [logging in to the Cloudflare dashboard](https://dash.cloudflare.com?to=/:account/workers/overview). From your **Account Home** > go to **Workers & Pages** > select your **Worker** > and select **Logs**. Logging is available for all customers, including those on the free plan.
 
 ![Cloudflare dashboard showing logs for a Worker named logging-example](../media/workers-logging-dashboard.png)
 
@@ -157,7 +157,11 @@ Other `11xx` errors generally indicate a problem with the Workers runtime itself
 
 ### Identifying errors: Workers Metrics
 
-You can find out whether your application is experiencing any downtime or returning any errors by navigating to **Account Home** > **Workers** > your **Worker** and reviewing your Worker's summary in **Resources**.
+To review whether your application is experiencing any downtime or returning any errors:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In **Account Home**, select **Workers & Pages**.
+3. Select your Worker and review your Worker's summary in **Metrics**.
 
 ### Debugging exceptions
 
diff --git a/content/workers/learning/metrics-and-analytics.md b/content/workers/learning/metrics-and-analytics.md
index ebe2b0b6dde..e80b1f49050 100644
--- a/content/workers/learning/metrics-and-analytics.md
+++ b/content/workers/learning/metrics-and-analytics.md
@@ -6,13 +6,17 @@ weight: 5
 
 # Metrics and analytics
 
-There are two graphical sources of information about your Workers traffic at a given time: Workers Metrics and zone-based Workers analytics. Workers metrics can help you diagnose issues and understand your Workers workloads by showing performance and usage of your Workers. If your Worker runs on a route on a zone, or on a few zones, go to **Workers** in your zone's Cloudflare dashboard to understand on a per-zone basis how much traffic your Worker is handling, and how many requests your site is getting.
+There are two graphical sources of information about your Workers traffic at a given time: Workers Metrics and zone-based Workers analytics. Workers metrics can help you diagnose issues and understand your Workers workloads by showing performance and usage of your Workers. If your Worker runs on a route on a zone, or on a few zones, go to **Workers & Pages** and select your Worker in your zone's Cloudflare dashboard to understand on a per-zone basis how much traffic your Worker is handling, and how many requests your site is getting.
 
 ---
 
 ## Workers metrics
 
-Workers metrics aggregate request data for an individual Worker script (if your Worker is running across multiple domains, and on `*.workers.dev`, metrics will aggregate requests across them). Select **Workers** > **Manage Workers** > your Worker to view its metrics.
+Workers metrics aggregate request data for an individual Worker script (if your Worker is running across multiple domains, and on `*.workers.dev`, metrics will aggregate requests across them). To view your Worker's metrics:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. Select **Workers & Pages**.
+3. Select your Worker to view its metrics.
 
 There are two metrics that can help you understand the health of your Worker in a given moment: requests success and error metrics, and invocation statuses.
 
diff --git a/content/workers/learning/migrating-to-module-workers.md b/content/workers/learning/migrating-to-module-workers.md
index 764a34dc525..676ba166513 100644
--- a/content/workers/learning/migrating-to-module-workers.md
+++ b/content/workers/learning/migrating-to-module-workers.md
@@ -88,7 +88,7 @@ export default worker;
 
 ## Module Workers in the dashboard
 
-The module Worker syntax has full support in the Cloudflare dashboard. Go to **Workers** > **Create a Service** > pick the HTTP Handler example > **Create Service**. After your service is created, select **Quick Edit** and it will launch the dashboard. Select **Send** at the top to test if your service is returning `“Hello world”`.
+The module Worker syntax has full support in the Cloudflare dashboard. Go to **Workers & Pages** > **Create** > **Worker** and pick the HTTP Handler example. After your Worker is created, select **Quick Edit** and it will launch the dashboard. Select **Send** at the top to test if your service is returning `“Hello world”`.
 
 Then replace:
 
diff --git a/content/workers/learning/playground.md b/content/workers/learning/playground.md
index 18ac87bc50b..5934d390500 100644
--- a/content/workers/learning/playground.md
+++ b/content/workers/learning/playground.md
@@ -42,7 +42,11 @@ To get familiar with Workers, experiment with the Playground by borrowing [Examp
 
 There are two versions of the Playground available: the [browser Playground](https://cloudflareworkers.com/#36ebe026bf3510a2e5acace89c09829f:about:blank) and the dashboard Playground, also known as the previewer.
 
-To access the dashboard Playground, log in to your Cloudflare account and go to **Account Home** > **Workers** > **your Worker script** > **Quick edit**.
+To access the dashboard Playground:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In **Account Home**, select **Workers & Pages**.
+3. Select your Worker and in your Worker, select **Quick edit**.
 
 When you have code you are ready to test, select **Save and Deploy** to preview at the bottom of the script panel.
 
diff --git a/content/workers/learning/using-durable-objects.md b/content/workers/learning/using-durable-objects.md
index 4b4781c1e9e..896b71f845b 100644
--- a/content/workers/learning/using-durable-objects.md
+++ b/content/workers/learning/using-durable-objects.md
@@ -25,8 +25,8 @@ Durable Objects are named instances of a class you define. Like a class in objec
 To start, enable Durable Objects for your account by purchasing Workers Paid:
 
  1. Log in to [the Cloudflare dashboard](https://dash.cloudflare.com/).
- 2. Go to **Workers** and select your Worker. 
- 3. In your Worker, scroll down to **Durable Objects** **Learn more** > **View Paid Plan**.
+ 2. Go to **Workers & Pages** and select your Worker. 
+ 3. In your Worker, scroll down to **Durable Objects** > **Learn more** > **View Paid Plan**.
  4. Select **Purchase Workers Paid** and complete the payment process to enable Durable Objects.
 
 There are three steps to creating and using a Durable Object:
diff --git a/content/workers/learning/using-services/index.md b/content/workers/learning/using-services/index.md
index ef880af953c..82a8c22fc03 100644
--- a/content/workers/learning/using-services/index.md
+++ b/content/workers/learning/using-services/index.md
@@ -17,7 +17,7 @@ To understand Workers Services better, it will help to know about Bindings and D
 
 ## Bindings
 
-Bindings allow your Workers to interact with resources on the Workers platform. Bindings can be configured by logging in to the Cloudflare dashboard > Account Home > [**Workers**](https://dash.cloudflare.com/?zone=workers) > your **Worker** > **Settings**> **Variables**. Bindings also provide a security model for interacting with those resources. Workers only have access to other resources that are explicitly defined as a binding in configuration.
+Bindings allow your Workers to interact with resources on the Workers platform. Bindings can be configured by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com) > Account Home > **Workers & Pages** > select your Worker > **Settings**> **Variables**. Bindings also provide a security model for interacting with those resources. Workers only have access to other resources that are explicitly defined as a binding in configuration.
 
 There are multiple types of bindings available today:
 
diff --git a/content/workers/platform/bindings/_index.md b/content/workers/platform/bindings/_index.md
index db5ef9b2c76..2aacb418ba3 100644
--- a/content/workers/platform/bindings/_index.md
+++ b/content/workers/platform/bindings/_index.md
@@ -15,7 +15,7 @@ There are multiple types of bindings available today.
 Bindings can be configured by one of two ways:
 
 * Updating your project's [`wrangler.toml` file](/workers/wrangler/configuration/#bindings).
-* Logging in to the [Cloudflare dashboard](https://dash.cloudflare.com) > Account Home > **Workers** > your **Worker** > **Settings**> **Variables**.
+* Logging in to the [Cloudflare dashboard](https://dash.cloudflare.com) > Account Home > **Workers & Pages** > your Worker > **Settings**> **Variables**.
 
 ### Service bindings
 
diff --git a/content/workers/platform/bindings/about-service-bindings.md b/content/workers/platform/bindings/about-service-bindings.md
index a3b0bb427ca..a2c6bac28ec 100644
--- a/content/workers/platform/bindings/about-service-bindings.md
+++ b/content/workers/platform/bindings/about-service-bindings.md
@@ -27,9 +27,10 @@ For more information, refer to the [Runtime API documentation for Service bindin
 
 To manage a Workers Service binding:
 
-1. Log in to the Cloudflare dashboard > Account Home > [Workers](https://dash.cloudflare.com/?zone=workers). 
-2. Select your **Worker**.
-3. Go to **Settings** > **Variables** > **Service bindings** > **Edit variables**. 
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In Account Home, select **Workers & Pages**.
+3. Select your **Worker**.
+4. Go to **Settings** > **Variables** > **Service bindings** > **Edit variables**. 
 
 ### Wrangler
 
@@ -68,9 +69,13 @@ Service bindings are available in your Worker code under the `<BINDING_NAME>` sp
 
 ### Connected Workers
 
-Workers bound to your Worker will be listed in [**Workers**](https://dash.cloudflare.com/?zone=workers) > your **Worker** > **Triggers** > **Bound Services**. Your team can easily view cross-service dependencies in this manner.
+To review Workers bound to your Worker in the Cloudflare dashboard:
 
-![Your team can view cross-service dependencies in the Cloudflare dashboard Account Home > Workers > Triggers](/workers/platform/bindings/media/service-bindings-triggers.png)
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. Select **Workers & Pages** and select your **Worker**.
+3. Go to **Triggers** > **Bound Services**. Your team can easily view cross-service dependencies in this manner.
+
+![Your team can view cross-service dependencies in the Cloudflare dashboard Account Home > Workers & Pages > your Worker > Triggers](/workers/platform/bindings/media/service-bindings-triggers.png)
 
 ## Compose an example Worker
 
@@ -80,7 +85,12 @@ In the following example, you will create a `gateway` Worker that invokes an `au
 
 First, you will create both a `gateway` and `auth` Worker. Once they are set up, go to the `gateway` Worker. In order to bind and call the [authentication](#authentication-workers-service) Worker, the `gateway` Worker needs to set up a Service binding. 
 
-To manage Service bindings, go to Account Home > [**Workers**](https://dash.cloudflare.com/?zone=workers) > your **Worker** > **Settings**> **Variables** > **Service bindings** > **Edit variables**.
+To manage Service bindings:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In Account Home, select **Workers & Pages**. 
+3. Select your Worker > **Settings**.
+4. In **Variables**, find **Service bindings** > **Edit variables**.
 
 ![Selecting Edit variables to create new bindings and edit existing bindings that enable Worker-to-Worker communication](/workers/platform/bindings/media/service-bindings.png)
 
diff --git a/content/workers/platform/deployments.md b/content/workers/platform/deployments.md
index 2885b33c4a0..5ecf891eb86 100644
--- a/content/workers/platform/deployments.md
+++ b/content/workers/platform/deployments.md
@@ -43,7 +43,13 @@ For more information on the `wrangler deployments list` and `wrangler deployment
 
 ### via the Cloudflare Dashboard
 
-Access deployments by logging into the [Cloudflare dashboard](https://dash.cloudflare.com) > **Account Home** > **Workers** > selecting your Worker project > **Deployments**. Deployments includes information about previous deployments, and your Worker’s detail page displays information about the most recently deployed and currently active deployment.
+To access your deployments:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In **Account Home**, select **Workers & Pages**.
+3. Select your Worker > **Deployments**. 
+
+Deployments includes information about previous deployments, and your Worker’s detail page displays information about the most recently deployed and currently active deployment.
 
 ### via the API
 
@@ -69,7 +75,7 @@ To perform a rollback via Wrangler, use the `wrangler rollback` command. Refer t
 To perform a rollback via the Cloudflare dashboard:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Go to **Workers** > select your Worker > **Deployments**. 
+2. Go to **Workers & Pages** > select your Worker > **Deployments**. 
 3. Find the deployment you would like to rollback to.
 4. Select the three dot icon on the right of the deployment and select **Rollback to this deployment**.
 
diff --git a/content/workers/platform/environment-variables.md b/content/workers/platform/environment-variables.md
index 65721a07e35..8312d9c011e 100644
--- a/content/workers/platform/environment-variables.md
+++ b/content/workers/platform/environment-variables.md
@@ -135,15 +135,16 @@ id = "<PRODUCTION KV NAMESPACEID>"
 
 ### Add environment variables via the dashboard
 
-Add environment variables by logging in to [Cloudflare dashboard](https://dash.cloudflare.com/) > **Account Home** > **Workers** and select your **Workers script**.
+To add environment variables, such as `vars` and `secret`, via the dashboard:
 
-To add environment variables, such as `vars` and `secret`:
-
-1.  Go to your **Workers script** > **Settings** > **Add variable** under **Environment Variables**.
-2.  Input a **Variable name** and its **value**, which will be made available to your Worker.
-3.  If your variable is a secret, select **Encrypt** to protect its value. This will prevent the value from being visible via Wrangler and the dashboard.
-4.  (Optional) To add multiple environment variables, select **Add variable**.
-5.  Select **Save** to implement your changes.
+1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. In **Account Home**, select **Workers & Pages**.
+3. Select your Worker > **Settings**.
+4. Under **Environment Variables**, select **Add variable**.
+5. Input a **Variable name** and its **value**, which will be made available to your Worker.
+6. If your variable is a secret, select **Encrypt** to protect its value. This will prevent the value from being visible via Wrangler and the dashboard.
+7. (Optional) To add multiple environment variables, select **Add variable**.
+8. Select **Save** to implement your changes.
 
 ![After selecting Add variable, you will be directed to an environment variables configuration page to set up your environment variable name and value](../media/env_variables_dash.png)
 
@@ -157,11 +158,13 @@ Do not select **Encrypt** when adding environment variables if your variable is
 
 To add KV namespace bindings:
 
-1.  Go to your **Workers script** > **Settings** > **Add binding** under **KV Namespace Bindings**.
-2.  Choose a **Variable name**. This will be the way the variable name will be referenced in your Worker script.
-3.  Next, select a **KV namespace** from the dropdown.
-4.  Select **Add binding** to add multiple bindings.
-5.  When you are finished, select **Save** to implement your changes.
+1.  Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. Select **Workers & Pages** and select your Worker.
+3. Select **Settings** > **Add binding** under **KV Namespace Bindings**.
+4. Choose a **Variable name**. This will be the way the variable name will be referenced in your Worker.
+5. Next, select a **KV namespace** from the dropdown.
+6. Select **Add binding** to add multiple bindings.
+7. When you are finished, select **Save** to implement your changes.
 
 ![After selecting add binding, you will be directed to a configuration page to specify your Variable name and KV namespace to create your binding](../media/kv_namespace_bindings.png)
 
diff --git a/content/workers/platform/environments.md b/content/workers/platform/environments.md
index 21a914ecb69..e45c2e1a818 100644
--- a/content/workers/platform/environments.md
+++ b/content/workers/platform/environments.md
@@ -65,7 +65,13 @@ Published my-worker
 
 #### Publishing to \*.workers.dev
 
-Your `*.workers.dev` subdomain allows you to deploy Workers [without attaching a custom domain as a Cloudflare zone](https://blog.cloudflare.com/announcing-workers-dev/). To claim a `*.workers.dev` subdomain, such as `my-subdomain.workers.dev`, select the **Workers** icon on your account home, or **Workers** then **Manage Workers** on your zone's dashboard, and begin setup on the right side of the Workers dashboard under **Your subdomain**.
+Your `*.workers.dev` subdomain allows you to deploy Workers [without attaching a custom domain as a Cloudflare zone](https://blog.cloudflare.com/announcing-workers-dev/). 
+
+To claim a `*.workers.dev` subdomain, such as `my-subdomain.workers.dev`:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. Select **Workers & Pages**.
+3. Find **Your subdomain** on the right-side menu and select **Change**.
 
 This `wrangler.toml` file has no environments defined and will publish `my-worker` to `my-worker.<your-subdomain>.workers.dev`:
 
diff --git a/content/workers/platform/limits.md b/content/workers/platform/limits.md
index 58ac3a26718..381663f3f71 100644
--- a/content/workers/platform/limits.md
+++ b/content/workers/platform/limits.md
@@ -182,7 +182,11 @@ Routes in fail closed mode will display a Cloudflare `1027` error page to visito
 
 Only one Workers instance runs on each of the many global Cloudflare global network servers. Each Workers instance can consume up to 128 MB of memory. Use [global variables](/workers/runtime-apis/web-standards/) to persist data between requests on individual nodes; note however, that nodes are occasionally evicted from memory.
 
-If a Worker processes a request that pushes the Worker over the 128MB limit, the Cloudflare Workers runtime may cancel one or more requests. To view these errors, as well as CPU limit overages, go to [**Workers**](https://dash.cloudflare.com/?to=/:account/workers) on the Cloudflare dashboard > **Manage Workers** > select the Worker you would like to investigate > scroll down to **Invocation Statuses** and examine _Exceeded Resources_.
+If a Worker processes a request that pushes the Worker over the 128MB limit, the Cloudflare Workers runtime may cancel one or more requests. To view these errors, as well as CPU limit overages:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. Select **Workers & Pages** > select the Worker you would like to investigate.
+3. Find **Invocation Statuses** and examine _Exceeded Resources_.
 
 Use the [TransformStream API](/workers/runtime-apis/streams/transformstream/) to stream responses if you are concerned about memory usage. This avoids loading an entire response into memory.
 
diff --git a/content/workers/platform/logpush.md b/content/workers/platform/logpush.md
index 41ab741bb27..3c5c68c3655 100644
--- a/content/workers/platform/logpush.md
+++ b/content/workers/platform/logpush.md
@@ -13,7 +13,7 @@ Workers Logpush requires a Wrangler version of `2.2.0` or higher. Check your ver
 
 To configure a Logpush job, verify that your Cloudflare account role can use Logpush. To check your role:
 
-1. Sign in to the [Cloudflare dashboard](https://dash.cloudflare.com). 
+1. Log in the [Cloudflare dashboard](https://dash.cloudflare.com). 
 2. Select your account and scroll down to **Manage Account** > **Members**.
 3. Check your account permissions. Roles with Logpush configuration access are different than Workers permissions. Super Administrators, Administrators, and the Log Share roles have full access to Logpush.
  
diff --git a/content/workers/platform/nodejs-compatibility.md b/content/workers/platform/nodejs-compatibility.md
index df74147732b..4060f9b5978 100644
--- a/content/workers/platform/nodejs-compatibility.md
+++ b/content/workers/platform/nodejs-compatibility.md
@@ -54,6 +54,6 @@ For additional options, refer to the list of [Pages-specific CLI commands](/work
 To enable Node.js for your Pages Function from the Cloudflare dashboard:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Select **Pages** and select your Pages project.
+2. Select **Workers & Pages** and select your Pages project.
 3. Select **Settings** > **Functions** > **Compatibility Flags**.
 4. Add the `nodejs_compat` compatibility flag to your Preview and Production deployments.
\ No newline at end of file
diff --git a/content/workers/platform/pricing.md b/content/workers/platform/pricing.md
index d9445d426d6..60f62c51619 100644
--- a/content/workers/platform/pricing.md
+++ b/content/workers/platform/pricing.md
@@ -41,9 +41,15 @@ Workers are available under two Usage Models: Bundled and Unbound. Usage Models
 
 #### Default usage model
 
-When an account is first upgraded to the Paid plan, the Unbound plan is used as the default Usage Model. You may change your default Usage Model account-wide by going to the **Account Home** > **Workers** > **Overview** > **Default Usage Model** > **Change**. Cloudflare recommends setting the default to the type of Worker you create the most. Existing Workers will not be impacted when changing the default Usage Model.
+When an account is first upgraded to the Paid plan, the Unbound plan is used as the default Usage Model. To change your default account-wide Usage Model:
 
-You may change the Usage Model for individual Workers without affecting your account-wide default. You can do this through the [`usage_model` key](/workers/wrangler/configuration/) in your `wranger.toml` file or through the dashboard: **Workers** > **select your Worker** > **Settings** > **Usage Model**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In Account Home, select **Workers & Pages**.
+3. Find **Default Usage Model** on the right-side menu > **Change**. 
+
+Cloudflare recommends setting the default to the type of Worker you create the most. Existing Workers will not be impacted when changing the default Usage Model.
+
+You may change the Usage Model for individual Workers without affecting your account-wide default. You can do this through the [`usage_model` key](/workers/wrangler/configuration/) in your `wranger.toml` file or through the dashboard: **Workers & Pages** > select your Worker > **Settings** > **Usage Model**.
 
 ### Same features
 
diff --git a/content/workers/platform/triggers/cron-triggers/index.md b/content/workers/platform/triggers/cron-triggers/index.md
index 59f63ba29fa..e27e5bed86c 100644
--- a/content/workers/platform/triggers/cron-triggers/index.md
+++ b/content/workers/platform/triggers/cron-triggers/index.md
@@ -12,7 +12,12 @@ Cron Triggers allow users to map a cron expression to a Worker script using a [S
 
 ## Add a Cron Trigger
 
-You can add Cron Triggers to Workers with the Cloudflare API, or in the dashboard in **Workers** > **Manage Workers** > select **your Worker** > [**Triggers**](https://dash.cloudflare.com/?to=/:account/workers). Refer to [Limits](/workers/platform/limits/) to track the maximum number of Cron Triggers per Worker. If a Worker is managed with Wrangler, [Cron Triggers should be exclusively managed through the `wrangler.toml`](/workers/wrangler/configuration/) file.
+Add Cron Triggers to Workers with the Cloudflare API, or in the dashboard. To add Cron Triggers in the Cloudflare dashboard:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. In Account Home, select your Worker > **Triggers** > **Cron Triggers**.
+
+Refer to [Limits](/workers/platform/limits/) to track the maximum number of Cron Triggers per Worker. If a Worker is managed with Wrangler, [Cron Triggers should be exclusively managed through the `wrangler.toml`](/workers/wrangler/configuration/) file.
 
 {{<Aside type="note" header="Requires a ScheduledEvent Listener">}}
 
diff --git a/content/workers/platform/triggers/custom-domains.md b/content/workers/platform/triggers/custom-domains.md
index be9f28c66f7..6e2c61ea338 100644
--- a/content/workers/platform/triggers/custom-domains.md
+++ b/content/workers/platform/triggers/custom-domains.md
@@ -29,7 +29,7 @@ You cannot create a Custom Domain on a hostname with an existing CNAME DNS recor
 To set up a Custom Domain in the dashboard:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Select **Workers** and select your Worker.
+2. Select **Workers & Pages** and select your Worker.
 3. Go to **Triggers** > **Custom Domains** > **Add Custom Domain**.
 4. Enter the domain you want to configure for your Worker.
 5. Select **Add Custom Domain**.
@@ -134,7 +134,7 @@ To migrate the route `example.com/*`:
 
 1. Log in to the [Cloudflare dashboard](https://dash.clouflare.com) and select your account.
 2. Go to **DNS** and delete the CNAME record for `example.com`.
-3. Go to **Account Home** > **Workers** > select your Worker > **Triggers**.
+3. Go to **Account Home** > **Workers & Pages** > select your Worker > **Triggers**.
 4. Select **Add Custom Domain** and add `example.com`.
 5. Delete the route `example.com/*` located in your Worker > **Triggers** > **Routes**.
 
diff --git a/content/workers/platform/triggers/routes.md b/content/workers/platform/triggers/routes.md
index c10e4997ee2..de819116c17 100644
--- a/content/workers/platform/triggers/routes.md
+++ b/content/workers/platform/triggers/routes.md
@@ -42,7 +42,7 @@ Before you set up a route, make sure you have a DNS record set up for the [domai
 To set up a route in the dashboard:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Go to **Workers** and select your Worker.
+2. Go to **Workers & Pages** and select your Worker.
 3. Go to **Triggers** > **Routes** > **Add route**.
 4. Enter the route and select the zone it applies to.
 5. Select **Add route**.
@@ -83,7 +83,7 @@ Cloudflare Workers accounts come with a `*.workers.dev` subdomain that is config
 To claim a `*.workers.dev` subdomain, such as `<YOUR_SUBDOMAIN>.workers.dev`:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. In **Account Home**, select **Workers**.
+2. In **Account Home**, select **Workers & Pages**.
 3. Select **Change** next to **Your subdomain**. The `name` field in your Worker configuration is used as the preview subdomain for the deployed Worker, (for example, `<YOUR_WORKER>.<YOUR_SUBDOMAIN>.workers.dev.`).
 
 When you create your Worker, the `workers.dev` route is automatically set up. Review this in your Worker > **Triggers** > **Routes**.
diff --git a/content/workers/runtime-apis/durable-objects.md b/content/workers/runtime-apis/durable-objects.md
index a504abe5f39..8069f6260be 100644
--- a/content/workers/runtime-apis/durable-objects.md
+++ b/content/workers/runtime-apis/durable-objects.md
@@ -5,7 +5,7 @@ title: Durable Objects
 
 # Durable Objects
 
-Durable Objects are available to anyone with a Workers paid subscription. You can enable them for your account in [the Cloudflare dashboard](https://dash.cloudflare.com/) by navigating to “Workers” and opting in to pricing.
+Durable Objects are available to anyone with a Workers paid subscription. Enable Durable Objects for your account by logging into the[the Cloudflare dashboard](https://dash.cloudflare.com/) > going to **Workers & Pages** > selecting your Worker and opting in to pricing.
 
 ## Background
 
diff --git a/content/workers/runtime-apis/kv.md b/content/workers/runtime-apis/kv.md
index 9c8214d62db..146f07cd108 100644
--- a/content/workers/runtime-apis/kv.md
+++ b/content/workers/runtime-apis/kv.md
@@ -11,7 +11,7 @@ Workers KV is a global, low-latency, key-value data store. It stores data in a s
 
 Learn more about [How KV works](/workers/learning/how-kv-works/).
 
-To use Workers KV, you must create a KV namespace and add a [binding](/workers/runtime-apis/kv/#kv-bindings) to your Worker. Refer to the [instructions for Wrangler KV commands](/workers/wrangler/workers-kv/) or the KV page of the [Workers dashboard](https://dash.cloudflare.com/?to=/:account/workers/kv/namespaces) to get started.
+To use Workers KV, you must create a KV namespace and add a [binding](/workers/runtime-apis/kv/#kv-bindings) to your Worker. Refer to the [instructions for Wrangler KV commands](/workers/wrangler/workers-kv/) on how to create a namespace with Wrangler. Create a KV namespace in the dashboard by logging into the [Cloudflare dashboard](https://dash.cloudflare.com) > select **Workers & Pages** > **KV**.
 
 The descriptions of KV methods below also contain links to Wrangler or REST API equivalents where appropriate, but using KV from your Worker is generally better for latency, scalability, and availability.
 
@@ -407,11 +407,12 @@ addEventListener("fetch", async (event) => {
 
 You can create a namespace [using Wrangler](/workers/wrangler/install-and-update/) or in the [Cloudflare dashboard](https://dash.cloudflare.com/). You can also bind the namespace to your Worker in the dashboard:
 
-1.  Go to **Workers**.
-2.  Select your **Worker**.
-3.  Select **Settings** > **Variables**.
-4.  Go to **KV Namespace Bindings**.
-5.  Select **Add binding**.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. Select **Workers & Pages**.
+2. Select your Worker.
+3. Select **Settings** > **Variables**.
+4. Go to **KV Namespace Bindings**.
+5. Select **Add binding**.
 
 {{</Aside>}}
 
diff --git a/content/workers/runtime-apis/nodejs/_index.md b/content/workers/runtime-apis/nodejs/_index.md
index c044176e4de..b38c8b02385 100644
--- a/content/workers/runtime-apis/nodejs/_index.md
+++ b/content/workers/runtime-apis/nodejs/_index.md
@@ -48,7 +48,7 @@ For additional options, refer to the list of [Pages-specific CLI commands](/work
 
 To enable Node.js for your Pages Function from the Cloudflare dashboard:
 
-1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Select **Pages** and select your Pages project.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
+2. Select **Workers & Pages** and select your Pages project.
 3. Select **Settings** > **Functions** > **Compatibility Flags**.
 4. Add the `nodejs_compat` compatibility flag to your Preview and Production deployments.
\ No newline at end of file
diff --git a/content/workers/tutorials/deploy-a-realtime-chat-app/index.md b/content/workers/tutorials/deploy-a-realtime-chat-app/index.md
index cfa92b8d288..5627f0e93cb 100644
--- a/content/workers/tutorials/deploy-a-realtime-chat-app/index.md
+++ b/content/workers/tutorials/deploy-a-realtime-chat-app/index.md
@@ -14,7 +14,7 @@ This chat application uses a Durable Object to control each chat room. Users con
 
 To continue with this tutorial, you must:
 1. Install [Wrangler v2](/workers/wrangler/install-and-update/).
-2. Purchase the Workers Paid plan and enable Durable Objects by logging into the [Cloudflare dashboard](https://dash.cloudflare.com) > **Workers** > **Resources** > **Durable Objects**.
+2. Purchase the Workers Paid plan and enable Durable Objects by logging into the [Cloudflare dashboard](https://dash.cloudflare.com) > **Workers & Pages** > select your Worker > **Durable Objects**.
 
 ## Clone the chat application repository
 
@@ -66,7 +66,7 @@ routes = [
 
 To test your live application:
 
-1. Open your `edge-chat-demo.<SUBDOMAIN>.workers.dev` subdomain. Your subdomain can be found in the [Cloudflare dashboard](https://dash.cloudflare.com) > **Workers** > your Worker > **Resources** > select the `edge-chat-demo.<SUBDOMAIN>.workers.dev` route.
+1. Open your `edge-chat-demo.<SUBDOMAIN>.workers.dev` subdomain. Your subdomain can be found in the [Cloudflare dashboard](https://dash.cloudflare.com) > **Workers & Pages** > your Worker > **Triggers** >  **Routes** > select the `edge-chat-demo.<SUBDOMAIN>.workers.dev` route.
 2. Enter a name in the **your name** field.
 3. Choose whether to enter a public room or create a private room.
 4. Send the link to other participants. You will be able to view room participants on the right side of the screen.
@@ -92,7 +92,7 @@ deleted_classes = ["ChatRoom", "RateLimiter"]
 
 Then run `wrangler publish`.
 
-To delete your Worker, log in to the [Cloudflare dashboard](https://dash.cloudflare.com) > **Workers** > your Worker > **Manage Service** > **Delete**. For complete instructions on set up and deletion, refer to the `README.md` in your cloned repository.
+To delete your Worker, log in to the [Cloudflare dashboard](https://dash.cloudflare.com) > **Workers & Pages** > **Manage Service** > **Delete**. For complete instructions on set up and deletion, refer to the `README.md` in your cloned repository.
 
 By completing this tutorial, you have deployed a real-time chat application with Durable Objects and Cloudflare Workers.
 
diff --git a/content/workers/tutorials/store-data-with-fauna/index.md b/content/workers/tutorials/store-data-with-fauna/index.md
index 469868d5089..23a6e1e7bac 100644
--- a/content/workers/tutorials/store-data-with-fauna/index.md
+++ b/content/workers/tutorials/store-data-with-fauna/index.md
@@ -872,7 +872,7 @@ export function getFaunaError(error) {
 
 ## Cleaning up
 
-To remove the resources you create in this tutorial, delete your Worker in the Cloudflare dashboard > **Workers** > **Manage Workers** > **your Worker** > **Settings** > **Delete**:
+To remove the resources you create in this tutorial, delete your Worker in the Cloudflare dashboard > **Workers & Pages** > select your Worker > **Manage Service** > **Delete**:
 
 ![Delete your Worker by following the steps above](./media/delete-worker.png)
 
diff --git a/content/workers/wrangler/deprecations.md b/content/workers/wrangler/deprecations.md
index d14dd5e54fb..32a0a8efffe 100644
--- a/content/workers/wrangler/deprecations.md
+++ b/content/workers/wrangler/deprecations.md
@@ -145,7 +145,7 @@ Try using `wrangler dev` to try out a worker during development.
 
 The `wrangler subdomain` command is no longer available for creating a `workers.dev` subdomain.
 
-Create the `workers.dev` subdomain on your Workers dashboard.
+Create the `workers.dev` subdomain in **Workers & Pages** > select your Worker > Your subdomain > **Change**.
 
 #### route