[Various] DashButton (#25461)

* bots

* bots - styling and fixes

* bots - partials

* missing import

* challenges

* ddos

* api shield

* api shield - partials

* missing import

Author: patriciasantaana

src/content/docs/api-shield/management-and-monitoring/api-routing.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 ---
 
-import { Markdown, Render, Steps, Tabs, TabItem } from "~/components"
+import { Markdown, Render, Steps, Tabs, TabItem, DashButton } from "~/components"
 
 API Shield Routing enables customers to create a unified external-facing API that routes requests to different back-end services that may have different paths and hosts than the existing zone and DNS configuration.
 
@@ -35,11 +35,12 @@ To create a route, you will need the operation ID of the Source Endpoint. To fin
     </TabItem>
     <TabItem label="New dashboard" icon="rocket">
         <Steps>
-            1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-            2. Select **Security** > **Web assets**.
-            3. Filter the endpoints to find your **Source Endpoint**.
-            4. Expand the row for your Source Endpoint and note the **operation ID** field.
-            5. Select the copy icon to copy the operation ID to your clipboard.
+            1. In the Cloudflare dashboard, go to the **Web Assets** page.
+
+                <DashButton url="/?to=/:account/:zone/security/web-assets" />
+            2. Filter the endpoints to find your **Source Endpoint**.
+            3. Expand the row for your Source Endpoint and note the **operation ID** field.
+            4. Select the copy icon to copy the operation ID to your clipboard.
         </Steps>
     </TabItem>
 </Tabs>
@@ -61,12 +62,13 @@ Once your Source Endpoints are added to Endpoint Management, use the following s
     </TabItem>
     <TabItem label="New dashboard" icon="rocket">
         <Steps>
-            1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-            2. Go to **Security** > **Web assets**.
-            3. In **Endpoints**, select an existing endpoint and expand its details.
-            4. Under **Routing**, select **Create route**.
-            5. Enter the target URL or IP address to route your endpoint to.
-            6. Select **Deploy route**.
+            1. In the Cloudflare dashboard, go to the **Web Assets** page.
+
+                <DashButton url="/?to=/:account/:zone/security/web-assets" />
+            2. In **Endpoints**, select an existing endpoint and expand its details.
+            3. Under **Routing**, select **Create route**.
+            4. Enter the target URL or IP address to route your endpoint to.
+            5. Select **Deploy route**.
         </Steps>
     </TabItem>
 </Tabs>

src/content/docs/api-shield/management-and-monitoring/developer-portal.mdx

@@ -6,7 +6,7 @@ sidebar:
   order: 5
 ---
 
-import { GlossaryTooltip, Tabs, TabItem, Steps } from "~/components";
+import { GlossaryTooltip, Tabs, TabItem, Steps, DashButton } from "~/components";
 
 Once your <GlossaryTooltip term="API endpoint">endpoints</GlossaryTooltip> are saved, API Shield doubles as an API catalog. API Shield can build an interactive documentation portal with the knowledge it has of your APIs, or you can upload a new OpenAPI schema file to build a documentation portal ad-hoc.
 
@@ -28,23 +28,23 @@ To create a developer portal:
       6. Select **Create pages project** to begin project creation. A new Pages project will be automatically created and your API schema will be automatically uploaded to the project along with other supporting static content.
       7. Select **Deploy site**.
     </Steps>
-
   </TabItem>
   <TabItem label="New dashboard" icon="rocket">
     <Steps>
-      1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-      2. Go to **Security** > **Settings**.
-      3. Filter by **API abuse**.
-      4. On **Create a developer portal**, select **Create site**.
-      5. Upload an OpenAPI v3.0 schema file or choose to select an existing schema from API Shield.
+      1. In the Cloudflare dashboard, go to the **Security Settings** page.
+
+          <DashButton url="/?to=/:account/:zone/security/settings" />
+      2. Filter by **API abuse**.
+      3. On **Create a developer portal**, select **Create site**.
+      4. Upload an OpenAPI v3.0 schema file or choose to select an existing schema from API Shield.
           :::note
           If you do not have a schema to upload or to select from a pre-existing schema, export your Endpoint Management schema. For best results, include the learned parameters.
 
           Only <GlossaryTooltip term="API schema">API schemas</GlossaryTooltip> uploaded to Schema validation 2.0 are available when selecting existing schemas.
           :::
-      6. Select **Download project files** to save a local copy of the files that will be uploaded to Cloudflare Pages. Downloading the project files can be helpful if you wish to modify the project in any way and then upload the new version manually to Pages.
-      7. Select **Create pages project** to begin project creation. A new Pages project will be automatically created and your API schema will be automatically uploaded to the project along with other supporting static content.
-      8. Select **Deploy site**.
+      5. Select **Download project files** to save a local copy of the files that will be uploaded to Cloudflare Pages. Downloading the project files can be helpful if you wish to modify the project in any way and then upload the new version manually to Pages.
+      6. Select **Create pages project** to begin project creation. A new Pages project will be automatically created and your API schema will be automatically uploaded to the project along with other supporting static content.
+      7. Select **Deploy site**.
     </Steps>
 
   </TabItem>

src/content/docs/api-shield/management-and-monitoring/endpoint-labels.mdx

@@ -7,7 +7,7 @@ sidebar:
   label: Labeling service
 ---
 
-import { Render, Steps, Tabs, TabItem } from "~/components";
+import { Render, Steps, Tabs, TabItem, DashButton } from "~/components";
 
 API Shield's labeling service will help you organize your endpoints and address vulnerabilities in your API. The labeling service comes with managed and user-defined labels.
 
@@ -110,18 +110,21 @@ Cloudflare will only add authentication labels to endpoints with successful resp
   </TabItem>
   <TabItem label="New dashboard" icon="rocket">
     <Steps>
-      1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-      2. Go to **Security** > **Settings**.
-      3. Filter by **API abuse**.
-      4. Under **Endpoint labels**, select **Manage labels**.
-      5. Name the label and add an optional label description.
-      6. Apply the label to your selected endpoints.
-      7. Select **Create label**.
+      1. In the Cloudflare dashboard, go to the **Security Settings** page.
+
+          <DashButton url="/?to=/:account/:zone/security/settings" />
+      2. Filter by **API abuse**.
+      3. Under **Endpoint labels**, select **Manage labels**.
+      4. Name the label and add an optional label description.
+      5. Apply the label to your selected endpoints.
+      6. Select **Create label**.
     </Steps>
         Alternatively, you can create a user-defined label via **Security** > **Web Assets**.
     <Steps>
-      1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-      2. Go to **Security** > **Web assets** > **Endpoints**.
+      1. In the Cloudflare dashboard, go to the **Web Assets** page.
+
+          <DashButton url="/?to=/:account/:zone/security/web-assets" />
+      2. Go to the **Endpoints** tab.
       3. Choose the endpoint that you want to label.
       4. Select **Edit endpoint labels**.
       5. Under **User**, select **Create user label**.
@@ -146,8 +149,10 @@ Cloudflare will only add authentication labels to endpoints with successful resp
   </TabItem>
   <TabItem label="New dashboard" icon="rocket">
     <Steps>
-      1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-      2. Go to **Security** > **Web assets** > **Endpoints**.
+      1. In the Cloudflare dashboard, go to the **Web Assets** page.
+
+          <DashButton url="/?to=/:account/:zone/security/web-assets" />
+      2. Go to the **Endpoints** tab.
       3. Choose the endpoint that you want to label.
       4. Select **Edit endpoint labels**.
       5. Add the label(s) that you want to use for the endpoint from the list of managed and user-defined labels.
@@ -170,13 +175,14 @@ Cloudflare will only add authentication labels to endpoints with successful resp
   </TabItem>
   <TabItem label="New dashboard" icon="rocket">
     <Steps>
-      1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-      2. Go to **Security** > **Settings**.
-      3. Filter by **API abuse**.
-      4. On **Endpoint labels**, select **Manage labels**.
-      5. On the existing label that you want to apply to multiple endpoints, select **Bulk apply**.
-      6. Choose the endpoints that you want to label by selecting its checkbox.
-      7. Select **Apply label**.
+      1. In the Cloudflare dashboard, go to the **Security Settings** page.
+
+          <DashButton url="/?to=/:account/:zone/security/settings" />
+      2. Filter by **API abuse**.
+      3. On **Endpoint labels**, select **Manage labels**.
+      4. On the existing label that you want to apply to multiple endpoints, select **Bulk apply**.
+      5. Choose the endpoints that you want to label by selecting its checkbox.
+      6. Select **Apply label**.
     </Steps>
   </TabItem>
 </Tabs>

src/content/docs/api-shield/management-and-monitoring/endpoint-management/index.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 ---
 
-import { GlossaryTooltip, Plan, Steps, Tabs, TabItem, Render } from "~/components"
+import { GlossaryTooltip, Plan, Steps, Tabs, TabItem, Render, DashButton } from "~/components"
 
 <Plan type="all" />
 
@@ -36,8 +36,10 @@ When an endpoint is using [Cloudflare Workers](/workers/), the metrics data will
   </TabItem>
   <TabItem label="New dashboard" icon="rocket">
     <Steps>
-      1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-      2. Go to **Security** > **Web assets** > **Endpoints**.
+      1. In the Cloudflare dashboard, go to the **Web Assets** page.
+
+          <DashButton url="/?to=/:account/:zone/security/web-assets" />
+      2. Go to the **Endpoints** tab.
       3. Select **Add endpoints**.
       4. Add your endpoints [manually](#add-endpoints-manually), from [Schema validation](#add-endpoints-from-schema-validation), or from [API Discovery](#add-endpoints-from-api-discovery).
     </Steps>

src/content/docs/api-shield/management-and-monitoring/endpoint-management/schema-learning.mdx

@@ -6,7 +6,7 @@ sidebar:
   order: 2
 ---
 
-import { Steps, Tabs, TabItem } from "~/components"
+import { Steps, Tabs, TabItem, DashButton } from "~/components"
 
 Cloudflare learns schema parameters via traffic inspection. For all endpoints saved to Endpoint Management, you can export the learned schema in OpenAPI `v3.0.0` format by hostname.
 
@@ -26,8 +26,10 @@ To protect your API with a learned schema, refer to [Schema validation](/api-shi
   </TabItem>
   <TabItem label="New dashboard" icon="rocket">
     <Steps>
-      1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-      2. Go to **Security** > **Web assets** > **Endpoints**.
+      1. In the Cloudflare dashboard, go to the **Web Assets** page.
+
+          <DashButton url="/?to=/:account/:zone/security/web-assets" />
+      2. Go to the **Endpoints** tab.
       3. Select **Export schema** and choose a hostname to export.
       4. Select whether to include learned parameters and rate limit recommendations
       5. Select **Export schema** and choose a location to save the file.

src/content/docs/api-shield/security/api-discovery.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 ---
 
-import { GlossaryTooltip, Render, Tabs, TabItem, Steps } from "~/components"
+import { GlossaryTooltip, Render, Tabs, TabItem, Steps, DashButton } from "~/components"
 
 Most development teams struggle to keep track of their APIs. Cloudflare API Discovery helps you map out and understand your attack surface area.
 
@@ -78,8 +78,10 @@ To access Machine Learning-based Discovery:
   </TabItem>
   <TabItem label="New dashboard" icon="rocket">
     <Steps>
-      1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
-      2. Go to **Web assets** > **Discovery**
+      1. In the Cloudflare dashboard, go to the **Web Assets** page.
+
+          <DashButton url="/?to=/:account/:zone/security/web-assets" />
+      2. Go to the **Discovery** tab.
       3. Filter the source results by `Session Identifier` or `Machine Learning` to view results from each Discovery method.
     </Steps>
   </TabItem>

src/content/docs/api-shield/security/authentication-posture.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 ---
 
-import { GlossaryTooltip, Render, Steps, Tabs, TabItem } from "~/components"
+import { GlossaryTooltip, Render, Steps, Tabs, TabItem, DashButton } from "~/components"
 
 Authentication Posture helps users identify authentication misconfigurations for APIs and alerts of their presence.
 
@@ -35,8 +35,10 @@ After configuring [session identifiers](/api-shield/get-started/#session-identif
   </TabItem>
   <TabItem label="New dashboard" icon="rocket">
     <Steps>
-      1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-      2. Go to **Security** > **Web assets** > **Endpoints**.
+      1. In the Cloudflare dashboard, go to the **Web Assets** page.
+
+          <DashButton url="/?to=/:account/:zone/security/web-assets" />
+      2. Go to the **Endpoints** tab.
       3. Filter your endpoints by the `cf-risk-missing-auth` or `cf-risk-mixed-auth` labels.
       4. Select an endpoint to see its authentication posture details on the endpoint details page.
       5. Choose between the 24-hour and 7-day view options, and note any authentication changes over time.

src/content/docs/api-shield/security/jwt-validation/index.mdx

@@ -6,7 +6,7 @@ sidebar:
 
 ---
 
-import { GlossaryTooltip, Steps, Tabs, TabItem, Render } from "~/components"
+import { GlossaryTooltip, Steps, Tabs, TabItem, Render, DashButton } from "~/components"
 
 
 <GlossaryTooltip term="JSON web token (JWT)">JSON web tokens (JWT)</GlossaryTooltip> are often used as part of an authentication component on many web applications today. Since JWTs are crucial to identifying users and their access, ensuring the token’s integrity is important.
@@ -34,13 +34,14 @@ A JWT validation configuration consists of creating a token validation configura
   </TabItem>
   <TabItem label="New dashboard" icon="rocket">
     <Steps>
-      1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-      2. Go to **Security** > **Settings**.
-      3. Filter by **API abuse**.
-      4. On **Token configurations**, select **Configure tokens**. If you already have one or more tokens, select **&lt;N> out of &lt;M> configurations used** instead.
-      5. Add a name for your configuration.
-      6. Choose where Cloudflare can locate the JWT for this configuration on incoming requests, such as a header or cookie and its name.
-      7. Copy and paste your JWT issuer's public key(s) (JWKS).
+      1. In the Cloudflare dashboard, go to the **Security Settings** page.
+          
+          <DashButton url="/?to=/:account/:zone/security/settings" />
+      2. Filter by **API abuse**.
+      3. On **Token configurations**, select **Configure tokens**.
+      4. Add a name for your configuration.
+      5. Choose where Cloudflare can locate the JWT for this configuration on incoming requests, such as a header or cookie and its name.
+      6. Copy and paste your JWT issuer's public key(s) (JWKS).
     </Steps>
   </TabItem>
 </Tabs>
@@ -69,18 +70,19 @@ To automatically keep your JWKS up to date when your identity provider refreshes
   </TabItem>
   <TabItem label="New dashboard" icon="rocket">
     <Steps>
-      1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-      2. Go to **Security** > **Security rules**.
-      3. On API JWT validation rules, select **Create rule**.
-      4. Add a name for your rule.
-      5. Select a hostname to protect requests with saved endpoints using the rule.
-      6. Deselect any endpoints that you want JWT validation to ignore (for example, an endpoint used to generate a JWT).
-      7. Select the token validation configuration that corresponds to the incoming requests.
-      8. Choose whether to strictly enforce token presence on these endpoints.
+      1. In the Cloudflare dashboard, go to the **Security rules** page.
+
+          <DashButton url="/?to=/:account/:zone/security/security-rules" />
+      2. On API JWT validation rules, select **Create rule**.
+      3. Add a name for your rule.
+      4. Select a hostname to protect requests with saved endpoints using the rule.
+      5. Deselect any endpoints that you want JWT validation to ignore (for example, an endpoint used to generate a JWT).
+      6. Select the token validation configuration that corresponds to the incoming requests.
+      7. Choose whether to strictly enforce token presence on these endpoints.
           - You may not expect 100% of clients to send in JWTs with their requests. If this is the case, choose *Ignore*. JWT validation will still validate JWTs that are present.
           - You may otherwise expect all requests to the selected hostname and endpoints to contain JWTs. If this is the case, choose *Mark as non-compliant*.
-      9. Choose an action to take for non-compliant requests. For example, JWTs that do not pass validation (expired, tampered with, or bad signature tokens) or requests with missing JWTs when *Mark as non-compliant* is selected in the previous step.
-      10. Select **Save**.
+      8. Choose an action to take for non-compliant requests. For example, JWTs that do not pass validation (expired, tampered with, or bad signature tokens) or requests with missing JWTs when *Mark as non-compliant* is selected in the previous step.
+      9. Select **Save**.
     </Steps>
   </TabItem>
 </Tabs>

src/content/docs/api-shield/security/jwt-validation/transform-rules.mdx

@@ -9,7 +9,7 @@ head:
     content: Enhance Transform Rules with JWT claims
 ---
 
-import { Steps } from "~/components"
+import { Steps, DashButton } from "~/components"
 
 You can forward information from a [JSON Web Token (JWT)](/api-shield/security/jwt-validation/) to the origin in a header by creating [Transform Rules](/rules/transform/) using claims that Cloudflare has verified via the JSON Web Token.
 
@@ -28,13 +28,14 @@ Refer to [Configure JWT validation](/api-shield/security/jwt-validation/api/) fo
 As an example, to send the `x-send-jwt-claim-user` request header to the origin, you must create a Transform Rule:
 
 <Steps>
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
-2. Go to **Rules** > **Overview**.
-3. Select **Create rule** > **Request Header Transform Rules**.
-4. Enter a rule name and a filter expression, if applicable.
-5. Choose **Set dynamic**.
-6. Set the header name to `x-send-jwt-claim-user`.
-7. Set the value to:
+1. In the Cloudflare dashboard, go to the **Rules overview** page.
+
+    <DashButton url="/?to=/:account/:zone/rules/overview" />
+2. Select **Create rule** > **Request Header Transform Rules**.
+3. Enter a rule name and a filter expression, if applicable.
+4. Choose **Set dynamic**.
+5. Set the header name to `x-send-jwt-claim-user`.
+6. Set the value to:
     ```txt wrap
     lookup_json_string(http.request.jwt.claims["<TOKEN_CONFIGURATION_ID>"][0], "claim_name")
     ```