[Chore] Rules changelog rationalization

Author: kodster28

public/__redirects

@@ -20,6 +20,7 @@
 /magic-transit/changelog/index.xml /changelog/rss/magic-transit.xml 301
 /magic-wan/changelog/index.xml /changelog/rss/magic-wan.xml 301
 /network-interconnect/changelog/index.xml /changelog/rss/network-interconnect.xml 301
+/rules/changelog/index.xml /changelog/rss/rules.xml 301
 /ssl/changelog/index.xml /changelog/rss/ssl.xml 301
 
 ## legacy

src/content/docs/rules/changelog.mdx

@@ -1,14 +1,117 @@
 ---
 pcx_content_type: changelog
 title: Changelog
-release_notes_file_name:
-  - rules
 sidebar:
   order: 25
 ---
 
-import { ProductReleaseNotes } from "~/components";
+import { ProductChangelog } from "~/components";
 
 {/* <!-- Actual content lives in /src/content/release-notes/rules.yaml. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
 
-<ProductReleaseNotes />
+<ProductChangelog product="rules"/>
+
+## 2024-09-20
+
+**Automatic DNS Validation for Cloudflare Rules**
+
+The Cloudflare dashboard now automatically validates [DNS records](https://developers.cloudflare.com/dns/proxy-status/) and [Cloudflare for SaaS custom hostnames](https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) for rules targeting specific hostnames or URLs. To prevent misconfigured rules and ensure smoother deployments, you will get proactive warnings for missing or misconfigured DNS records and custom hostnames.
+
+## 2024-09-17
+
+**Compression Rules available to all plans with Zstandard support**
+
+[Compression Rules](https://developers.cloudflare.com/rules/compression-rules/) now support Zstandard compression and are available in all Cloudflare plans. Users in the Free plan will gradually get access throughout 2024.
+
+## 2024-09-13
+
+**Snippets now available in beta**
+
+[Cloudflare Snippets](https://developers.cloudflare.com/rules/snippets/) have transitioned from alpha to beta.
+
+## 2024-09-10
+
+**wildcard\_replace() function now supported in URL rewrites**
+
+You can now use the [`wildcard_replace()`](https://developers.cloudflare.com/ruleset-engine/rules-language/functions/#wildcard_replace) function in rewrite expressions of [URL rewrites](https://developers.cloudflare.com/rules/transform/url-rewrite/).
+
+## 2024-09-05
+
+**New Rules Templates for one-click rule creation**
+
+The new **Rules** > **Templates** page in the Cloudflare dashboard allows you to create common rules with a single click, featuring dozens of pre-built templates. You can also access these templates directly from each product's rule builder. Also, explore the [Examples gallery](https://developers.cloudflare.com/rules/examples/) in the developer docs for real-world use cases and inspiration.
+
+## 2024-08-22
+
+**Simplified UI for Single Redirects with wildcard support**
+
+The simplified UI for [Single Redirects](https://developers.cloudflare.com/rules/url-forwarding/single-redirects/) is now available to all users, making URL redirects easier and more intuitive. This update builds on the recent [wildcard support](https://developers.cloudflare.com/ruleset-engine/rules-language/functions/#wildcard_replace) in Ruleset Engine products. Access the new UI under **Rules > Redirect Rules**. Learn more about wildcard support and our open-source Rust crate in the [blog post](https://blog.cloudflare.com/wildcard-rules).
+
+## 2024-08-20
+
+**Cloud Connector now available to all customers**
+
+Cloud Connector (beta) is now available to all customers. For setup details, refer to the [documentation](https://developers.cloudflare.com/rules/cloud-connector/), explore [examples](https://developers.cloudflare.com/rules/cloud-connector/examples/), and check out the [blog post](https://blog.cloudflare.com/cloud-connector).
+
+## 2024-08-16
+
+**Cloud Connector now available to all free customers**
+
+Cloud Connector (beta) is now available to all free and a subset of paid customers. This rollout will be [gradually extended](https://developers.cloudflare.com/rules/cloud-connector/#availability) to all Cloudflare users, simplifying multi-cloud management and enhancing integration with Cloudflare's Connectivity Cloud. For more information, refer to the [blog post](https://blog.cloudflare.com/cloud-connector).
+
+## 2024-08-12
+
+**Cloudflare Snippets limits have been upgraded**
+
+Cloudflare Snippets (alpha) now allow multiple subrequests depending on your plan. For more information, refer to the [Availability](https://developers.cloudflare.com/rules/snippets/#availability).
+
+## 2024-07-31
+
+**Wildcard support added to Ruleset Engine products**
+
+Wildcards are now supported across our Ruleset Engine-based products, including Single Redirects, Cache Rules, Transform Rules, WAF, Waiting Room, and more:
+
+* You can now use the `wildcard` and `strict wildcard` operators with any string field in the Ruleset Engine, such as full URI, host, headers, cookies, user-agent, and country. For more details, refer to [Operators](https://developers.cloudflare.com/ruleset-engine/rules-language/operators/) and [Wildcard matching](https://developers.cloudflare.com/ruleset-engine/rules-language/operators/#wildcard-matching).
+* In [Single Redirects](https://developers.cloudflare.com/rules/url-forwarding/single-redirects/), the `wildcard_replace()` function allows you to use segments matched by the `wildcard` and `strict wildcard` operators in redirect URL targets. For more information, refer to [Functions](https://developers.cloudflare.com/ruleset-engine/rules-language/functions/#wildcard_replace).
+
+## 2024-07-01
+
+**Cloudflare Snippets now available to all paid customers**
+
+Cloudflare Snippets (alpha) are now available to all paid customers.
+
+## 2024-06-03
+
+**Cloudflare Snippets now available to all Enterprise customers**
+
+Cloudflare Snippets (alpha) are now available to all Enterprise customers. Customers in other paid plans will gradually get access throughout 2024.
+
+## 2024-05-14
+
+**Page Rules migration**
+
+The [Page Rules migration guide](https://developers.cloudflare.com/rules/reference/page-rules-migration/) is now available for users interested in transitioning to modern Rules features instead of Page Rules. Explore the guide for detailed instructions on migrating your configurations.
+
+## 2024-05-13
+
+**New Configuration Rules setting for Web Analytics (RUM)**
+
+You can now turn off Cloudflare Web Analytics, also known as Real User Monitoring (RUM), for specific requests using a configuration rule.
+
+## 2024-04-29
+
+**New Configuration Rules setting for Cloudflare Fonts**
+
+You can now turn on or off Cloudflare Fonts for specific requests using a configuration rule.
+
+## 2024-03-22
+
+**New TLS fields in rule expressions**
+
+Customers can now use new fields `cf.tls_client_hello_length` (the length of the client hello message sent in a TLS handshake), `cf.tls_client_random` (the value of the 32-byte random value provided by the client in a TLS handshake), and `cf.tls_client_extensions_sha1` (the SHA-1 fingerprint of TLS client extensions) in various products built on Ruleset Engine.
+
+## 2024-03-20
+
+**Origin Rules now allow port numbers in Host Header Override**
+
+Customers can now use arbitrary port numbers in Host Header Override in Origin Rules. Previously, only hostname was allowed as a value (for example, `example.com`). Now, you can set the value to `hostname:port` (for example, `example.com:1234`) as well.