[WAF, Rules] Remove single-use partials (#24548)

---------

Co-authored-by: Maddy <[email protected]>

Author: 2 people

src/content/docs/fundamentals/manage-domains/redirect-domain.mdx

@@ -1,10 +1,9 @@
 ---
 pcx_content_type: reference
 title: Redirect one domain to another
-
 ---
 
-import { Render } from "~/components"
+import { Render, Example } from "~/components";
 
 If you have an alias domain that only forwards traffic to another domain (that is, the domain does not have an associated origin server of its own), you can set up redirects directly within Cloudflare.
 
@@ -21,4 +20,31 @@ If you have an alias domain that only forwards traffic to another domain (that i
 
 3. Use [Redirect rules](/rules/url-forwarding/) to forward traffic from your alias domain to your other domain.
 
-   <Render file="url-forwarding/different-hostname-example" product="rules" />
+This example will redirect all requests for `smallshop.example.com` to a different hostname using HTTPS, keeping the original path and query string.
+
+   <Example>
+
+   **When incoming requests match**
+   - **Field:** _Hostname_
+   - **Operator:** _equals_
+   - **Value:** `smallshop.example.com`
+
+   If you are using the Expression Editor, enter the following expression:<br/>
+   `(http.host eq "smallshop.example.com")`
+
+   **Then**
+   - **Type:** _Dynamic_
+   - **Expression:** `concat("https://globalstore.example.net", http.request.uri.path)`
+   - **Status code:** _301_
+   - **Preserve query string:** Enabled
+
+   </Example>
+
+   For example, the redirect rule would perform the following redirects:
+
+   | Request URL                                           | Target URL                                               | Status code |
+   | ----------------------------------------------------- | -------------------------------------------------------- | ----------- |
+   | `http://smallshop.example.com/`                       | `https://globalstore.example.net/`                       | `301`       |
+   | `http://smallshop.example.com/admin/?logged_out=true` | `https://globalstore.example.net/admin/?logged_out=true` | `301`       |
+   | `https://smallshop.example.com/?all_items=1`          | `https://globalstore.example.net/?all_items=1`           | `301`       |
+   | `http://example.com/about/`                           | (unchanged)                                              | n/a         |

src/content/docs/learning-paths/application-security/firewall/managed-rules.mdx

@@ -3,15 +3,16 @@ title: Managed Rules
 pcx_content_type: overview
 sidebar:
   order: 2
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 <Render file="waf-managed-rules-intro" product="waf" />
 
 ## Rulesets
 
 By default, Cloudflare offers the following rulesets:
 
-<Render file="waf-rulesets" product="waf" />
+- [Cloudflare Managed Ruleset](/waf/managed-rules/reference/cloudflare-managed-ruleset/)
+- [Cloudflare OWASP Core Ruleset](/waf/managed-rules/reference/owasp-core-ruleset/)
+- [Cloudflare Exposed Credentials Check Managed Ruleset](/waf/managed-rules/reference/exposed-credentials-check/)

src/content/docs/rules/index.mdx

@@ -15,12 +15,11 @@ import {
 	LinkTitleCard,
 	Plan,
 	RelatedProduct,
-	Render,
 } from "~/components";
 
 <Plan type="all" />
 
-<Render file="rules-definition" />
+Cloudflare Rules allows you to make adjustments to requests and responses, configure Cloudflare settings, and trigger specific actions for matching requests.
 
 Rules features require that you [proxy the DNS records](/dns/proxy-status/) of your domain (or subdomain) through Cloudflare.
 
@@ -83,8 +82,8 @@ Rules features require that you [proxy the DNS records](/dns/proxy-status/) of y
 	href="/rules/custom-errors/"
 	cta="Configure Custom Errors"
 >
-	Define what custom content to serve for errors returned by an origin server
-	or by a Cloudflare product, including Workers.
+	Define what custom content to serve for errors returned by an origin server or
+	by a Cloudflare product, including Workers.
 </Feature>
 
 ---

src/content/docs/rules/page-rules/how-to/url-forwarding.mdx

@@ -7,16 +7,15 @@ sidebar:
 head:
   - tag: title
     content: URL forwarding | Page Rules
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Page Rules allow you to forward or redirect traffic to a different URL, though they are just one of the [options provided by Cloudflare](/fundamentals/reference/redirects/).
 
 <Render file="page-rules-migration" />
 
-***
+---
 
 ## Redirect with Page Rules
 
@@ -27,13 +26,15 @@ To configure URL forwarding or redirects using Page Rules:
 3. Under **Page Rules**, select **Create Page Rule**.
 4. Under **If the URL matches**, enter the URL or URL pattern that should match the rule. 
 5. In **Pick a Setting**, choose **Forwarding URL** from the drop-down menu.
-6. For **Select status code**, choose *301 - Permanent Redirect* or *302 - Temporary Redirect*.
+6. For **Select status code**, choose _301 - Permanent Redirect_ or _302 - Temporary Redirect_.
 7. Enter the destination URL.
 8. Select **Save and Deploy Page Rule**.
 
-<Render file="page-rule-proxied-dns-warning" />
+:::note
+Page Rules require a [proxied DNS record](/dns/proxy-status/) to work. Page Rules will not apply to subdomains that do not exist in DNS or are not being directed to Cloudflare.
+:::
 
-***
+---
 
 ## Forwarding examples
 
@@ -67,7 +68,7 @@ https://example.com/products
 
 If you enter the address above in the forwarding box and select **Add Rule**, within a few seconds any requests that match the pattern you entered will automatically be forwarded with an `HTTP 302` redirect status code to the new URL.
 
-***
+---
 
 ## Advanced forwarding options
 

src/content/docs/waf/managed-rules/check-for-exposed-credentials/test-configuration.mdx

@@ -16,6 +16,7 @@ After enabling and configuring exposed credentials checks, you may want to test
 
 Cloudflare provides a special set of case-sensitive credentials for this purpose:
 
-<Render file="exposed-creds-test-credentials" />
+- Login: `CF_EXPOSED_USERNAME` or `[email protected]`
+- Password: `CF_EXPOSED_PASSWORD`
 
 The WAF always considers these specific credentials as having been previously exposed. Use them to force an "exposed credentials" event, which allows you to check the behavior of your current configuration.

src/content/docs/waf/tools/security-level.mdx

@@ -4,12 +4,24 @@ source: https://support.cloudflare.com/hc/en-us/articles/200170056-Understanding
 title: Security Level
 ---
 
-import { Render } from "~/components";
+In the old Cloudflare dashboard, security level has the value _Always protected_ and you cannot change this setting. To turn [Under Attack mode](/fundamentals/reference/under-attack-mode/) on or off, use the separate toggle.
 
-<Render file="security-level-scores" product="waf" />
+In the new security dashboard, the Cloudflare API, and in Terraform, use security level to turn Under Attack mode on or off.
 
-<Render file="threat-score-definition" product="waf" />
+Cloudflare's [Under Attack mode](/fundamentals/reference/under-attack-mode/) performs additional security checks to help mitigate layer 7 DDoS attacks. When you enable Under Attack mode, Cloudflare will present a JS challenge page.
 
+:::caution
 
+Only use [Under Attack mode](/fundamentals/reference/under-attack-mode/) when a website is under a DDoS attack. Under Attack mode may affect some actions on your domain, such as your API traffic.
 
----
+To enable or disable Under Attack mode for your API or any other part of your domain, create a [configuration rule](/rules/configuration-rules/).
+
+:::
+
+## Threat score
+
+Previously, a threat score represented a Cloudflare threat score from 0–100, where 0 indicates low risk. Now, the threat score is always `0` (zero).
+
+:::note[Recommendation]
+Currently we do not recommend creating rules based on the threat score, since this score is no longer being populated.
+:::