[API Shield] Sequence rules new dash (#23642)

* sequence rules new dash

* endpoints pt1

* feedback

Author: patriciasantaana

src/content/docs/api-shield/api-gateway.mdx

@@ -25,7 +25,7 @@ APIs are fundamental to modern applications but are increasingly targeted by mal
 
 ### Management and Monitoring tools
 
-- **[Endpoint Management](/api-shield/management-and-monitoring/endpoint-management/)**: Gain visibility into your API endpoints, including discovery of shadow APIs and monitoring of active endpoints.
+- **[Endpoint management](/api-shield/management-and-monitoring/endpoint-management/)**: Gain visibility into your API endpoints, including discovery of shadow APIs and monitoring of active endpoints.
 
 - **[Analytics and logging](/api-shield/security/sequence-analytics/)**: Access detailed analytics and logs to monitor API usage, performance, and security events.
 

src/content/docs/api-shield/changelog.mdx

@@ -21,7 +21,7 @@ API Shield now automatically labels endpoints with risks due to missing schemas
 
 **API Authentication Posture**
 
-Customers will see per-endpoint authentication details inside API Shield's [Endpoint Management](/api-shield/management-and-monitoring/) for zones with configured session identifiers.
+Customers will see per-endpoint authentication details inside [Endpoints](/api-shield/management-and-monitoring/) for zones with configured session identifiers.
 
 ## 2024-12-19
 
@@ -33,7 +33,7 @@ API Shield now automatically labels endpoints with risks due to authentication s
 
 **Endpoint labels**
 
-Customers can now organize their endpoints by use case and custom labels in [Endpoint Management](/api-shield/management-and-monitoring/endpoint-labels/) for easy reference and future machine learning (ML) model training.
+Customers can now organize their endpoints by use case and custom labels using the [Endpoint labeling service](/api-shield/management-and-monitoring/endpoint-labels/) for easy reference and future machine learning (ML) model training.
 
 ## 2024-10-18
 
@@ -49,9 +49,9 @@ Customers can now enable the [Fallthrough Action](/api-shield/security/schema-va
 
 ## 2024-08-28
 
-**Increased capacity for Endpoint Management and Schema Validation**
+**Increased capacity for Endpoint management and Schema Validation**
 
-Endpoint Management and Schema Validation now support up to 10,000 saved and validated API endpoints.
+Endpoint management and Schema Validation now support up to 10,000 saved and validated API endpoints.
 
 ## 2024-07-08
 
@@ -79,6 +79,6 @@ Customers can now build [Sequence Mitigation](/api-shield/security/sequence-miti
 
 ## 2024-02-23
 
-**Endpoint Management supports hostname variables**
+**Endpoint management supports hostname variables**
 
-Customers can now save endpoints in [Endpoint Management](/api-shield/management-and-monitoring/) that contain variables in the hostname. Hostname variables are supported across all product features.
+Customers can now save endpoints in [Endpoint management](/api-shield/management-and-monitoring/) that contain variables in the hostname. Hostname variables are supported across all product features.

src/content/docs/api-shield/security/sequence-mitigation/manage-sequence-rules.mdx

@@ -10,33 +10,60 @@ head:
     content: Manage sequence rules
 
 ---
-import { Steps } from "~/components"
+import { Steps, Tabs, TabItem } from "~/components"
 
 ## Create a sequence rule
 
-<Steps>
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
-2. Go to **Security** > **API Shield** > **API Rules**.
-3. Select **Create sequence rule**.
-4. <a id="rule-form"/>
-   Name your rule.
-5. Select a starting endpoint. This is the endpoint that you expect users to hit first in their request flow when using your API.
-   - Choose a hostname to display the list of endpoints for that hostname.
-   - Choose an endpoint.
-   - Select **Set as starting endpoint**.
-6. Select a final endpoint. This is the endpoint you are targeting for protection.
-   - Choose a hostname to display the list of endpoints for that hostname.
-   - Choose an endpoint.
-   - Select **Set as ending endpoint**.
-7. Choose an action that corresponds to the security model type:
-   - **Allow**: This will create a positive security model by defining approved sequences on your API.
-   - **Log** / **Block**: This will test or enforce a negative security model defining known bad sequences on your API. 
-      :::note
-
-      If you chose **Allow**, select whether to log or block the request to the final endpoint when users do not first request the starting endpoint in the sequence. 
-      :::
-8. Select **Create rule**.
-</Steps>
+<Tabs syncKey="dashNewNav">
+   <TabItem label="Old dashboard">
+      <Steps>
+         1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
+         2. Go to **Security** > **API Shield** > **API Rules**.
+         3. Select **Create sequence rule**.
+         4. Name your rule.
+         5. Select a starting endpoint. This is the endpoint that you expect users to hit first in their request flow when using your API.
+               - Choose a hostname to display the list of endpoints for that hostname.
+               - Choose an endpoint.
+               - Select **Set as starting endpoint**.
+         6. Select a final endpoint. This is the endpoint you are targeting for protection.
+               - Choose a hostname to display the list of endpoints for that hostname.
+               - Choose an endpoint.
+               - Select **Set as ending endpoint**.
+         7. Choose an action that corresponds to the security model type:
+               - **Allow**: This will create a positive security model by defining approved sequences on your API.
+               - **Log** / **Block**: This will test or enforce a negative security model defining known bad sequences on your API. 
+                  :::note
+
+                  If you chose **Allow**, select whether to log or block the request to the final endpoint when users do not first request the starting endpoint in the sequence. 
+                  :::
+         8. Select **Create rule**.
+      </Steps>
+   </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 **Security** > **Security rules**.
+         3. Select **Create rule** and choose **API sequence rules**.
+         4. Name your rule.
+         5. Select a starting endpoint. This is the endpoint that you expect users to hit first in their request flow when using your API.
+               - Choose a hostname to display the list of endpoints for that hostname.
+               - Choose an endpoint.
+               - Select **Set as starting endpoint**.
+         6. Select a final endpoint. This is the endpoint you are targeting for protection.
+               - Choose a hostname to display the list of endpoints for that hostname.
+               - Choose an endpoint.
+               - Select **Set as ending endpoint**.
+         7. Choose an action that corresponds to the security model type:
+               - **Allow**: This will create a positive security model by defining approved sequences on your API.
+               - **Log** / **Block**: This will test or enforce a negative security model defining known bad sequences on your API. 
+                  :::note
+
+                  If you chose **Allow**, select whether to log or block the request to the final endpoint when users do not first request the starting endpoint in the sequence. 
+                  :::
+         8. Select **Create rule**.
+      </Steps>
+   </TabItem>
+</Tabs>
 
 ## Edit a sequence rule