diff --git a/src/content/docs/learning-paths/workers/get-started/first-application.mdx b/src/content/docs/learning-paths/workers/get-started/first-application.mdx
index b2cd561a284cdfa..9d69e0693aa5983 100644
--- a/src/content/docs/learning-paths/workers/get-started/first-application.mdx
+++ b/src/content/docs/learning-paths/workers/get-started/first-application.mdx
@@ -7,6 +7,7 @@ sidebar:
order: 3
---
+import { DashButton } from "~/components";
## Build an AI application with Hono and Workers
diff --git a/src/content/docs/learning-paths/workers/get-started/first-worker.mdx b/src/content/docs/learning-paths/workers/get-started/first-worker.mdx
index ed3a3262ec3904b..8e1bb44fffa1559 100644
--- a/src/content/docs/learning-paths/workers/get-started/first-worker.mdx
+++ b/src/content/docs/learning-paths/workers/get-started/first-worker.mdx
@@ -5,7 +5,7 @@ sidebar:
order: 2
---
-import { Render, PackageManagers } from "~/components";
+import { Render, PackageManagers, DashButton } from "~/components";
## Build and deploy your first Worker
diff --git a/src/content/docs/workers/ci-cd/builds/configuration.mdx b/src/content/docs/workers/ci-cd/builds/configuration.mdx
index db7014a6ccca1b5..e575732c0cb20d5 100644
--- a/src/content/docs/workers/ci-cd/builds/configuration.mdx
+++ b/src/content/docs/workers/ci-cd/builds/configuration.mdx
@@ -6,7 +6,7 @@ sidebar:
order: 2
---
-import { DirectoryListing, Render, Tabs, TabItem } from "~/components";
+import { DirectoryListing, Render, Tabs, TabItem, DashButton } from "~/components";
When connecting your Git repository to your Worker, you can customize the configurations needed to build and deploy your Worker.
@@ -89,10 +89,12 @@ You can provide custom environment variables to your build.
To add environment variables via the dashboard:
- 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
- 2. In **Account Home**, select **Workers & Pages**.
- 3. In **Overview**, select your Worker.
- 4. Select **Settings** > **Environment variables**.
+ 1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+
+
+ 2. In **Overview**, select your Worker.
+ 3. Select **Settings** > **Environment variables**.
To add env variables using Wrangler, define text and JSON via the `[vars]` configuration in your Wrangler file.
diff --git a/src/content/docs/workers/ci-cd/external-cicd/github-actions.mdx b/src/content/docs/workers/ci-cd/external-cicd/github-actions.mdx
index 0dd072dcf9b3548..7da89c8c4a3f34d 100644
--- a/src/content/docs/workers/ci-cd/external-cicd/github-actions.mdx
+++ b/src/content/docs/workers/ci-cd/external-cicd/github-actions.mdx
@@ -3,6 +3,7 @@ pcx_content_type: how-to
title: GitHub Actions
description: Integrate Workers development into your existing GitHub Actions workflows.
---
+import { DashButton } from "~/components";
You can deploy Workers with [GitHub Actions](https://github.com/marketplace/actions/deploy-to-cloudflare-workers-with-wrangler). Here is how you can set up your GitHub Actions workflow.
@@ -17,12 +18,13 @@ To find your Cloudflare account ID, refer to [Find account and zone IDs](/fundam
### API token
To create an API token to authenticate Wrangler in your CI job:
+1. In the Cloudflare dashboard, go to the **Account API tokens** page.
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com).
-2. Select **Manage Account** > **Account API Tokens**.
-3. Select **Create Token** > find **Edit Cloudflare Workers** > select **Use Template**.
-4. Customize your token name.
-5. Scope your token.
+
+
+2. Select **Create Token** > find **Edit Cloudflare Workers** > select **Use Template**.
+3. Customize your token name.
+4. Scope your token.
You will need to choose the account and zone resources that the generated API token will have access to. We recommend scoping these down as much as possible to limit the access of your token. For example, if you have access to three different Cloudflare accounts, you should restrict the generated API token to only the account on which you will be deploying a Worker.
diff --git a/src/content/docs/workers/configuration/cron-triggers.mdx b/src/content/docs/workers/configuration/cron-triggers.mdx
index 294ce3e8915d3e6..0a02d5bef2f4ee1 100644
--- a/src/content/docs/workers/configuration/cron-triggers.mdx
+++ b/src/content/docs/workers/configuration/cron-triggers.mdx
@@ -5,7 +5,7 @@ head: []
description: Enable your Worker to be executed on a schedule.
---
-import { Render, WranglerConfig, TabItem, Tabs } from "~/components";
+import { Render, WranglerConfig, TabItem, Tabs, DashButton } from "~/components";
## Background
@@ -113,9 +113,11 @@ crons = ["0 * * * *"]
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 **Workers & Pages**.
-3. In **Overview**, select your Worker > **Settings** > **Triggers** > **Cron Triggers**.
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+
+
+2. In **Overview**, select your Worker > **Settings** > **Triggers** > **Cron Triggers**.
## Supported cron expressions
@@ -195,11 +197,13 @@ curl "http://localhost:8787/cdn-cgi/handler/scheduled?cron=*+*+*+*+*&time=174585
To view the execution history of Cron Triggers, view **Cron Events**:
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. In Account Home, go to **Workers & Pages**.
-3. In **Overview**, select your **Worker**.
-4. Select **Settings**.
-5. Under **Trigger Events**, select **View events**.
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+
+
+2. In **Overview**, select your **Worker**.
+3. Select **Settings**.
+4. Under **Trigger Events**, select **View events**.
Cron Events stores the 100 most recent invocations of the Cron scheduled event. [Workers Logs](/workers/observability/logs/workers-logs) also records invocation logs for the Cron Trigger with a longer retention period and a filter & query interface. If you are interested in an API to access Cron Events, use Cloudflare's [GraphQL Analytics API](/analytics/graphql-api).
@@ -217,8 +221,11 @@ Refer to [Metrics and Analytics](/workers/observability/metrics-and-analytics/)
To delete a Cron Trigger on a deployed Worker via the dashboard:
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Go to **Workers & Pages**, and select your Worker.
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+
+
+2. Select your Worker.
3. Go to **Triggers** > select the three dot icon next to the Cron Trigger you want to remove > **Delete**.
#### Via the [Wrangler configuration file](/workers/wrangler/configuration/)
@@ -252,12 +259,14 @@ Renewable energy can be purchased in a number of ways, including through on-site
Green Compute can be configured at the account level:
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. In Account Home, select **Workers & Pages**.
-3. In the **Account details** section, find **Compute Setting**.
-4. Select **Change**.
-5. Select **Green Compute**.
-6. Select **Confirm**.
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+
+
+2. In the **Account details** section, find **Compute Setting**.
+3. Select **Change**.
+4. Select **Green Compute**.
+5. Select **Confirm**.
## Related resources
diff --git a/src/content/docs/workers/configuration/environment-variables.mdx b/src/content/docs/workers/configuration/environment-variables.mdx
index 1a2ac65a52a9a35..62af6defcb250e9 100644
--- a/src/content/docs/workers/configuration/environment-variables.mdx
+++ b/src/content/docs/workers/configuration/environment-variables.mdx
@@ -5,7 +5,7 @@ head: []
description: You can add environment variables, which are a type of binding, to attach text strings or JSON values to your Worker.
---
-import { Render, TabItem, Tabs, WranglerConfig } from "~/components";
+import { Render, TabItem, Tabs, WranglerConfig, DashButton } from "~/components";
## Background
@@ -79,15 +79,16 @@ Learn about [environments in Wrangler](/workers/wrangler/environments).
## Add environment variables via the dashboard
To add environment variables via the dashboard:
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
-1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
-2. Select **Workers & Pages**.
-3. In **Overview**, select your Worker.
-4. Select **Settings**.
-5. Under **Variables and Secrets**, select **Add**.
-6. Select a **Type**, input a **Variable name**, and input its **Value**. This variable will be made available to your Worker.
-7. (Optional) To add multiple environment variables, select **Add variable**.
-8. Select **Deploy** to implement your changes.
+
+
+2. In **Overview**, select your Worker.
+3. Select **Settings**.
+4. Under **Variables and Secrets**, select **Add**.
+5. Select a **Type**, input a **Variable name**, and input its **Value**. This variable will be made available to your Worker.
+6. (Optional) To add multiple environment variables, select **Add variable**.
+7. Select **Deploy** to implement your changes.
:::caution[Plaintext strings and secrets]
Select the **Secret** type if your environment variable is a [secret](/workers/configuration/secrets/). Alternatively, consider [Cloudflare Secrets Store](/secrets-store/), for account-level secrets.
diff --git a/src/content/docs/workers/configuration/routing/custom-domains.mdx b/src/content/docs/workers/configuration/routing/custom-domains.mdx
index 1c091634f3bce93..8fb4b295a78f7d3 100644
--- a/src/content/docs/workers/configuration/routing/custom-domains.mdx
+++ b/src/content/docs/workers/configuration/routing/custom-domains.mdx
@@ -4,7 +4,7 @@ title: Custom Domains
---
-import { WranglerConfig } from "~/components";
+import { WranglerConfig, DashButton } from "~/components";
## Background
@@ -27,7 +27,7 @@ To add a Custom Domain, you must have:
1. An [active Cloudflare zone](/dns/zone-setups/).
2. A Worker to invoke.
-Custom Domains can be attached to your Worker via the [Cloudflare dashboard](/workers/configuration/routing/custom-domains/#set-up-a-custom-domain-in-the-dashboard), [Wrangler](/workers/configuration/routing/custom-domains/#set-up-a-custom-domain-in-your-wrangler-configuration-file) or the [API](/api/resources/workers/subresources/domains/methods/list/).
+Custom Domains can be attached to your Worker via the Cloudflare dashboard, [Wrangler](/workers/configuration/routing/custom-domains/#set-up-a-custom-domain-in-your-wrangler-configuration-file) or the [API](/api/resources/workers/subresources/domains/methods/list/).
:::caution
@@ -41,8 +41,11 @@ 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 & Pages** and in **Overview**, select your Worker.
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+
+
+2. In **Overview**, select your Worker.
3. Go to **Settings** > **Domains & Routes** > **Add** > **Custom Domain**.
4. Enter the domain you want to configure for your Worker.
5. Select **Add Custom Domain**.
@@ -149,21 +152,28 @@ If you are currently invoking a Worker using a [route](/workers/configuration/ro
### Migrate from Routes via the dashboard
To migrate the route `example.com/*`:
+1. In the Cloudflare dashboard, go to the **Account home** page.
+
+
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Go to **DNS** and delete the CNAME record for `example.com`.
-3. Go to **Account Home** > **Workers & Pages**.
-4. In **Overview**, select your Worker > **Settings** > **Domains & Routes**.
-5. Select **Add** > **Custom domain** and add `example.com`.
-6. Delete the route `example.com/*` located in your Worker > **Settings** > **Domains & Routes**.
+2. Select your domain.
+3. Go to **DNS** and delete the CNAME record for `example.com`.
+4. Go to **Account Home** > **Workers & Pages**.
+5. In **Overview**, select your Worker > **Settings** > **Domains & Routes**.
+6. Select **Add** > **Custom domain** and add `example.com`.
+7. Delete the route `example.com/*` located in your Worker > **Settings** > **Domains & Routes**.
### Migrate from Routes via Wrangler
To migrate the route `example.com/*` in your [Wrangler configuration file](/workers/wrangler/configuration/):
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Go to **DNS** and delete the CNAME record for `example.com`.
-3. Add the following to your Wrangler file:
+1. In the Cloudflare dashboard, go to the **Account home** page.
+
+
+
+2. Select your domain.
+3. Go to **DNS** and delete the CNAME record for `example.com`.
+4. Add the following to your Wrangler file:
diff --git a/src/content/docs/workers/configuration/routing/routes.mdx b/src/content/docs/workers/configuration/routing/routes.mdx
index 1fec3a061f6bb53..dee5a1d8b7a4de2 100644
--- a/src/content/docs/workers/configuration/routing/routes.mdx
+++ b/src/content/docs/workers/configuration/routing/routes.mdx
@@ -3,7 +3,7 @@ pcx_content_type: concept
title: Routes
---
-import { WranglerConfig } from "~/components";
+import { WranglerConfig, DashButton } from "~/components";
## Background
@@ -42,9 +42,11 @@ Routes can also be created via the API. Refer to the [Workers Routes API documen
Before you set up a route, make sure you have a DNS record set up for the [domain](/dns/manage-dns-records/how-to/create-zone-apex/) or [subdomain](/dns/manage-dns-records/how-to/create-subdomain/) you would like to route to.
To set up a route in the dashboard:
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Go to **Workers & Pages** and in **Overview**, select your Worker.
+
+
+2. In **Overview**, select your Worker.
3. Go to **Settings** > **Domains & Routes** > **Add** > **Route**.
4. Select the zone and enter the route pattern.
5. Select **Add route**.
@@ -71,7 +73,7 @@ zone_id = ""
-Add the `zone_name` or `zone_id` option after each route. The `zone_name` and `zone_id` options are interchangeable. If using `zone_id`, find your zone ID by logging in to the [Cloudflare dashboard](https://dash.cloudflare.com) > select your account > select your website > find the **Zone ID** in the lefthand side of **Overview**.
+Add the `zone_name` or `zone_id` option after each route. The `zone_name` and `zone_id` options are interchangeable. If using `zone_id`, find your zone ID by logging in to the Cloudflare dashboard > select your account > select your website > find the **Zone ID** in the left-hand side of **Overview**.
To add multiple routes:
diff --git a/src/content/docs/workers/configuration/versions-and-deployments/gradual-deployments.mdx b/src/content/docs/workers/configuration/versions-and-deployments/gradual-deployments.mdx
index 986ca63cbcc0f7c..32470ad93ff9115 100644
--- a/src/content/docs/workers/configuration/versions-and-deployments/gradual-deployments.mdx
+++ b/src/content/docs/workers/configuration/versions-and-deployments/gradual-deployments.mdx
@@ -5,7 +5,7 @@ head: []
description: Incrementally deploy code changes to your Workers with gradual deployments.
---
-import { Example } from "~/components";
+import { Example, DashButton } from "~/components";
Gradual Deployments give you the ability to incrementally deploy new [versions](/workers/configuration/versions-and-deployments/#versions) of Workers by splitting traffic across versions.
@@ -19,7 +19,7 @@ Using gradual deployments, you can:
## Use gradual deployments
-The following section guides you through an example usage of gradual deployments. You will choose to use either [Wrangler](/workers/configuration/versions-and-deployments/gradual-deployments/#via-wrangler) or the [Cloudflare dashboard](/workers/configuration/versions-and-deployments/gradual-deployments/#via-the-cloudflare-dashboard) to:
+The following section guides you through an example usage of gradual deployments. You will choose to use either [Wrangler](/workers/configuration/versions-and-deployments/gradual-deployments/#via-wrangler) or the Cloudflare dashboard to:
- Create a new Worker.
- Publish a new version of that Worker without deploying it.
@@ -88,9 +88,11 @@ npx wrangler versions deploy
### Via the Cloudflare dashboard
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/workers) and select your account.
-2. Go to **Workers & Pages**.
-3. Select **Create application** > **Hello World** template > deploy your Worker.
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+
+
+2. Select **Create application** > **Hello World** template > deploy your Worker.
4. Once the Worker is deployed, go to the online code editor through **Edit code**. Edit the Worker code (change the `Response` content) and upload the Worker.
5. To save changes, select the **down arrow** next to **Deploy** > **Save**. This will create a new version of your Worker.
6. Create a new deployment that splits traffic between the two versions created in step 3 and 5 by going to **Deployments** and selecting **Deploy Version**.
@@ -157,7 +159,7 @@ curl -s https://example.com -H 'Cloudflare-Workers-Version-Overrides: my-worker-
The dictionary can contain multiple key-value pairs. Each key indicates the name of the Worker the override should be applied to. The value indicates the version ID that should be used and must be a [String](https://www.rfc-editor.org/rfc/rfc8941#name-strings).
-A version override will only be applied if the specified version is in the current deployment. The versions in the current deployment can be found using the [`wrangler deployments list`](/workers/wrangler/commands/#list-5) command or on the [Workers Dashboard](https://dash.cloudflare.com/?to=/:account/workers) under Worker > Deployments > Active Deployment.
+A version override will only be applied if the specified version is in the current deployment. The versions in the current deployment can be found using the [`wrangler deployments list`](/workers/wrangler/commands/#list-5) command or on the **Workers & Pages** page of the Cloudflare dashboard > Select your Workers > Deployments > Active Deployment.
:::note[Verifying that the version override was applied]
diff --git a/src/content/docs/workers/configuration/versions-and-deployments/index.mdx b/src/content/docs/workers/configuration/versions-and-deployments/index.mdx
index 607ec00ce18063b..bb0f74f1074599b 100644
--- a/src/content/docs/workers/configuration/versions-and-deployments/index.mdx
+++ b/src/content/docs/workers/configuration/versions-and-deployments/index.mdx
@@ -4,6 +4,7 @@ title: Versions & Deployments
head: []
description: Upload versions of Workers and create deployments to release new versions.
---
+import { DashButton } from "~/components";
Versions track changes to your Worker. Deployments configure how those changes are deployed to your traffic.
@@ -83,9 +84,11 @@ Wrangler allows you to view the 10 most recent versions and deployments. Refer t
To view your deployments in the Cloudflare dashboard:
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/workers) and select your account.
-2. Go to **Workers & Pages**.
-3. Select your Worker > **Deployments**.
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+
+
+2. Select your Worker > **Deployments**.
## Limits
diff --git a/src/content/docs/workers/examples/103-early-hints.mdx b/src/content/docs/workers/examples/103-early-hints.mdx
index e96cc6463f384d7..497f7c111a2e841 100644
--- a/src/content/docs/workers/examples/103-early-hints.mdx
+++ b/src/content/docs/workers/examples/103-early-hints.mdx
@@ -13,6 +13,7 @@ sidebar:
order: 1001
description: Allow a client to request static assets while waiting for the HTML response.
---
+import { DashButton } from "~/components";
If you want to get started quickly, click on the button below.
@@ -26,7 +27,10 @@ import { TabItem, Tabs } from "~/components";
To ensure Early Hints are enabled on your zone:
-1. Log in to the [Cloudflare Dashboard](https://dash.cloudflare.com) and select your account and website.
+1. In the Cloudflare dashboard, go to the **Account home** page.
+
+
+
2. Go to **Speed** > **Optimization** > **Content Optimization**.
3. Enable the **Early Hints** toggle to on.
diff --git a/src/content/docs/workers/examples/images-workers.mdx b/src/content/docs/workers/examples/images-workers.mdx
index 3694bc3ea7ea81a..5989b071ae97e28 100644
--- a/src/content/docs/workers/examples/images-workers.mdx
+++ b/src/content/docs/workers/examples/images-workers.mdx
@@ -13,6 +13,7 @@ sidebar:
description: Set up custom domain for Images using a Worker or serve images
using a prefix path and Cloudflare registered domain.
---
+import { DashButton } from "~/components";
If you want to get started quickly, click on the button below.
@@ -23,10 +24,11 @@ This creates a repository in your GitHub account and deploys the application to
import { TabItem, Tabs } from "~/components";
To serve images from a custom domain:
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com).
-2. Select your account > select **Workers & Pages**.
-3. Select **Create application** > **Workers** > **Create Worker** and create your Worker.
+
+
+2. Select **Create application** > **Workers** > **Create Worker** and create your Worker.
4. In your Worker, select **Quick edit** and paste the following code.
diff --git a/src/content/docs/workers/get-started/dashboard.mdx b/src/content/docs/workers/get-started/dashboard.mdx
index 453c667064c3fed..87d7dc32a35dc3c 100644
--- a/src/content/docs/workers/get-started/dashboard.mdx
+++ b/src/content/docs/workers/get-started/dashboard.mdx
@@ -8,9 +8,9 @@ head:
content: Get started - Dashboard
---
-import { Render } from "~/components";
+import { Render, DashButton } from "~/components";
-Follow this guide to create a Workers application using [the Cloudflare dashboard](https://dash.cloudflare.com).
+Follow this guide to create a Workers application using the Cloudflare dashboard.
@@ -22,13 +22,15 @@ Follow this guide to create a Workers application using [the Cloudflare dashboar
To get started with a new Workers application:
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Go to the **Workers & Pages** section of the dashboard.
-2. Select [Create](https://dash.cloudflare.com/?to=/:account/workers-and-pages/create). From here, you can:
- * You can select from the gallery of production-ready templates
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+
+
+3. Select **Create application**. From here, you can:
+ * Select from the gallery of production-ready templates
* Import an existing Git repository on your own account
* Let Cloudflare clone and bootstrap a public repository containing a Workers application.
-3. Once you've connected to your chosen [Git provider](/workers/ci-cd/builds/git-integration/github-integration/), configure your project and click `Deploy`.
+3. Once you have connected to your chosen [Git provider](/workers/ci-cd/builds/git-integration/github-integration/), configure your project and select **Deploy**.
4. Cloudflare will kick off a new build and deployment. Once deployed, preview your Worker at its provided `workers.dev` subdomain.
## Continue development
diff --git a/src/content/docs/workers/observability/logs/real-time-logs.mdx b/src/content/docs/workers/observability/logs/real-time-logs.mdx
index a41e7b60968e136..f60c4050d6bb8ba 100644
--- a/src/content/docs/workers/observability/logs/real-time-logs.mdx
+++ b/src/content/docs/workers/observability/logs/real-time-logs.mdx
@@ -8,7 +8,7 @@ sidebar:
order: 3
---
-import { TabItem, Tabs, Steps } from "~/components";
+import { TabItem, Tabs, DashButton } from "~/components";
With Real-time logs, access all your log events in near real-time for log events happening globally. Real-time logs is helpful for immediate feedback, such as the status of a new deployment.
@@ -23,14 +23,13 @@ Real-time logs are not available for zones on the [Cloudflare China Network](/ch
## View logs from the dashboard
To view real-time logs associated with any deployed Worker using the Cloudflare dashboard:
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
-
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. In Account Home, go to **Workers & Pages**.
-3. In **Overview**, select your **Worker**.
-4. Select **Logs**.
-5. In the right-hand navigation bar, select **Live**.
-
+
+
+2. In **Overview**, select your **Worker**.
+3. Select **Logs**.
+4. In the right-hand navigation bar, select **Live**.
## View logs using `wrangler tail`
diff --git a/src/content/docs/workers/platform/pricing.mdx b/src/content/docs/workers/platform/pricing.mdx
index 4db79c4caedebb6..559a34610024d09 100644
--- a/src/content/docs/workers/platform/pricing.mdx
+++ b/src/content/docs/workers/platform/pricing.mdx
@@ -7,7 +7,7 @@ head: []
description: Workers plans and pricing information.
---
-import { GlossaryTooltip, Render } from "~/components";
+import { GlossaryTooltip, Render, DashButton } from "~/components";
By default, users have access to the Workers Free plan. The Workers Free plan includes limited usage of Workers, Pages Functions, Workers KV and Hyperdrive. Read more about the [Free plan limits](/workers/platform/limits/#worker-limits).
@@ -113,15 +113,18 @@ Changing the usage model only affects billable usage, and has no technical impli
To change your default account-wide usage model:
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/workers-and-pages) and select your account.
-2. In Account Home, select **Workers & Pages**.
-3. Find **Usage Model** on the right-side menu > **Change**.
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+
+
+2. Find **Usage Model** on the right-side menu > **Change**.
Usage models may be changed at the individual Worker level:
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/workers/services/view/:worker/production/settings) and select your account.
-2. In Account Home, select **Workers & Pages**.
-3. In **Overview**, select your Worker > **Settings** > **Usage Model**.
+2. In **Overview**, select your Worker > **Settings** > **Usage Model**.
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 usage model.
diff --git a/src/content/docs/workers/tutorials/automated-analytics-reporting/index.mdx b/src/content/docs/workers/tutorials/automated-analytics-reporting/index.mdx
index 0cb75dad87e6068..0843677add8c374 100644
--- a/src/content/docs/workers/tutorials/automated-analytics-reporting/index.mdx
+++ b/src/content/docs/workers/tutorials/automated-analytics-reporting/index.mdx
@@ -21,6 +21,7 @@ import {
TabItem,
Tabs,
WranglerConfig,
+ DashButton,
} from "~/components";
In this tutorial, you will create a [Cloudflare Worker](https://workers.cloudflare.com/) that fetches analytics data about your account from Cloudflare's [GraphQL Analytics API](https://developers.cloudflare.com/analytics/graphql-api/). You will be able to view the account analytics data in your browser and receive a scheduled email report.
@@ -445,9 +446,11 @@ Once you put the secrets, preview your analytics data at `account-analytics.
+
+2. Select `account-analytics` Worker.
3. Go to **Settings** > **Domains & Routes**.
diff --git a/src/content/docs/workers/tutorials/deploy-a-realtime-chat-app/index.mdx b/src/content/docs/workers/tutorials/deploy-a-realtime-chat-app/index.mdx
index 83d6cc231cdfad8..82331cc05eb47dd 100644
--- a/src/content/docs/workers/tutorials/deploy-a-realtime-chat-app/index.mdx
+++ b/src/content/docs/workers/tutorials/deploy-a-realtime-chat-app/index.mdx
@@ -9,7 +9,7 @@ tags:
- JavaScript
---
-import { Render, WranglerConfig } from "~/components";
+import { Render, WranglerConfig, DashButton } from "~/components";
In this tutorial, you will deploy a serverless, real-time chat application that runs using [Durable Objects](/durable-objects/).
@@ -75,10 +75,14 @@ custom_domain = true
To test your live application:
-1. Open your `edge-chat-demo..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..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.
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+
+
+2. Select your Worker > **Triggers** > **Routes** > Select the `edge-chat-demo..workers.dev` route.
+3. Enter a name in the **your name** field.
+4. Choose whether to enter a public room or create a private room.
+5. Send the link to other participants. You will be able to view room participants on the right side of the screen.
## Uninstall your application
@@ -108,11 +112,12 @@ deleted_classes = ["ChatRoom", "RateLimiter"]
Then run `npx wrangler deploy`.
To delete your Worker:
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. In Account Home, select **Workers & Pages**.
-3. In **Overview**, select your Worker.
-4. Select **Manage Service** > **Delete**. For complete instructions on set up and deletion, refer to the `README.md` in your cloned repository.
+2. In **Overview**, select your Worker.
+3. Select **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/src/content/docs/workers/tutorials/using-prisma-postgres-with-workers/index.mdx b/src/content/docs/workers/tutorials/using-prisma-postgres-with-workers/index.mdx
index 1d0df6d1bd02d0a..7ce0042da7b97fd 100644
--- a/src/content/docs/workers/tutorials/using-prisma-postgres-with-workers/index.mdx
+++ b/src/content/docs/workers/tutorials/using-prisma-postgres-with-workers/index.mdx
@@ -10,7 +10,7 @@ tags:
- PostgreSQL
---
-import { PackageManagers } from "~/components";
+import { PackageManagers, DashButton } from "~/components";
[Prisma Postgres](https://www.prisma.io/postgres) is a managed, serverless PostgreSQL database. It supports features like connection pooling, caching, real-time subscriptions, and query optimization recommendations.
@@ -220,7 +220,7 @@ npm run deploy
The `wrangler` CLI will bundle and upload your application.
-If you are not already logged in, the `wrangler` CLI will open a browser window prompting you to log in to the [Cloudflare dashboard](https://dash.cloudflare.com/).
+If you are not already logged in, the `wrangler` CLI will open a browser window prompting you to log in to the Cloudflare dashboard.
:::note
If you belong to multiple accounts, select the account where you want to deploy the project.
diff --git a/src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx b/src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx
index b3bc19457cb8a5f..f7ab8f2da856e2d 100644
--- a/src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx
+++ b/src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/commands.mdx
@@ -9,7 +9,7 @@ head:
noindex: true
---
-import { Render, Type, MetaInfo, WranglerConfig } from "~/components";
+import { Render, Type, MetaInfo, WranglerConfig, DashButton } from "~/components";
@@ -107,7 +107,14 @@ wrangler logout
This command only invalidates OAuth tokens acquired through the `wrangler login` command. However, it will try to delete the configuration file regardless of your authorization method.
-If you wish to delete your API token, log in to the Cloudflare dashboard and go to **Overview** > **Get your API token** in the right side menu > select the three-dot menu on your Wrangler token and select **Delete** if you wish to delete your API token.
+To delete your API token:
+
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+
+
+2. In the **Overview** > **Get your API token** in the right side menu.
+3. Select the three-dot menu on your Wrangler token and select **Delete**.
---
@@ -166,7 +173,7 @@ After you have registered a subdomain, add `workers_dev` to your Wrangler file.
To publish to your own domain, specify these three fields in your Wrangler file.
- `zone_id` string
- - The Cloudflare zone ID, for example, `zone_id = "b6558acaf2b4cad1f2b51c5236a6b972"`, which can be found in the [Cloudflare dashboard](https://dash.cloudflare.com).
+ - The Cloudflare zone ID, for example, `zone_id = "b6558acaf2b4cad1f2b51c5236a6b972"`, which can be found in the Cloudflare dashboard.
- `route` string
- The route you would like to publish to, for example, `route = "example.com/my-worker/*"`.
diff --git a/src/content/partials/workers/get-started-dash.mdx b/src/content/partials/workers/get-started-dash.mdx
index 18e9fa067e279d0..63f3c464720f5e4 100644
--- a/src/content/partials/workers/get-started-dash.mdx
+++ b/src/content/partials/workers/get-started-dash.mdx
@@ -2,9 +2,12 @@
{}
---
+import { DashButton } from "~/components";
To create your first Worker using the Cloudflare dashboard:
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Select **Workers & Pages** > **Create application**.
+
+
+2. Select **Create application**.
3. Select **Create Worker** > **Deploy**.