Merge branch 'cloudflare:production' into feature/content-version-management-system

Author: shinchan79

.github/CODEOWNERS

@@ -203,7 +203,7 @@
 
 # Support
 
-/src/content/docs/support/ @shanecloudflare @zeinjaber @TracyCloudflare @ngayerie @cloudflare/pcx-technical-writing
+/src/content/docs/support/ @shanecloudflare @zeinjaber @TracyCloudflare @ngayerie @cloudflare/pcx-technical-writing @cloudflare/customer-support
 
 # Turnstile
 

CONTRIBUTING.md

@@ -33,9 +33,46 @@ If we require more information to address your pull request, the `more-informati
 - [npm](https://nodejs.org/en/learn/getting-started/an-introduction-to-the-npm-package-manager#introduction-to-npm) is the recommended package manager that must be used in installing dependencies.
 - The generated `package-lock.json` file must be committed to git.
 
+## Wrangler config
+
+If you're adding a code snippet to the docs that represents a Wrangler config file (`wrangler.toml` or `wrangler.json`) make sure you wrap it with the `<WranglerConfig>` component, which ensure it's rendered as both JSON and TOML e.g.
+
+````
+
+import { WranglerConfig } from "~/components";
+
+<WranglerConfig>
+
+```toml
+# Top-level configuration
+name = "my-worker"
+main = "src/index.js"
+compatibility_date = "2022-07-12"
+
+workers_dev = false
+route = { pattern = "example.org/*", zone_name = "example.org" }
+
+kv_namespaces = [
+  { binding = "<MY_NAMESPACE>", id = "<KV_ID>" }
+]
+
+[env.staging]
+name = "my-worker-staging"
+route = { pattern = "staging.example.org/*", zone_name = "example.org" }
+
+kv_namespaces = [
+  { binding = "<MY_NAMESPACE>", id = "<STAGING_KV_ID>" }
+]
+```
+
+</WranglerConfig>
+
+````
 
 ## Workers Playground
+
 If you are adding a code snippet to the docs that is:
+
 1. A fully contained, valid Worker (i.e. it does not require external dependencies or specific bindings)
 2. Only JavaScript
 
@@ -58,6 +95,7 @@ export default {
 };
 ```
 ````
+
 would render as
 
 <img width="870" alt="Screenshot 2024-02-20 at 14 29 22" src="https://github.com/cloudflare/cloudflare-docs/assets/28503158/56aa8016-b3b6-4d64-8213-b1a26f16534a">

package-lock.json

@@ -39,6 +39,7 @@
 		"@cloudflare/workers-types": "^4.20241112.0",
 		"@codingheads/sticky-header": "^1.0.2",
 		"@iconify-json/material-symbols": "^1.2.8",
+		"@iarna/toml": "^2.2.5",
 		"@stoplight/json-schema-tree": "^4.0.0",
 		"@types/dompurify": "^3.2.0",
 		"@types/hast": "^3.0.4",
@@ -61,14 +62,15 @@
 		"he": "^1.2.0",
 		"instantsearch.css": "^8.5.1",
 		"instantsearch.js": "^4.75.4",
+		"jsonc-parser": "^3.3.1",
 		"lz-string": "^1.5.0",
 		"marked": "^15.0.2",
 		"mdast-util-mdx-expression": "^2.0.1",
 		"mermaid": "^11.4.0",
 		"node-html-parser": "^6.1.13",
 		"patch-package": "^8.0.0",
 		"playwright": "^1.49.0",
-		"prettier": "^3.3.3",
+		"prettier": "^3.4.1",
 		"prettier-plugin-astro": "^0.14.1",
 		"puppeteer": "^23.9.0",
 		"react": "^18.3.1",

package.json

@@ -0,0 +1,54 @@
+---
+import { parse } from "node-html-parser";
+import { Code, Tabs, TabItem } from "@astrojs/starlight/components";
+import TOML from "@iarna/toml";
+import { parse as jsoncParse } from "jsonc-parser";
+
+const slot = await Astro.slots.render("default");
+
+const html = parse(slot);
+
+const copy = html.querySelector("div.copy > button");
+
+if (!copy) {
+	throw new Error(
+		`[WranglerConfig] Unable to find copy button in rendered code block HTML.`,
+	);
+}
+
+let code = copy.attributes["data-code"];
+
+if (!code) {
+	throw new Error(
+		`[WranglerConfig] Unable to find data-code attribute on copy button.`,
+	);
+}
+
+code = code.replace(/\u007f/g, "\n");
+
+const language =
+	html.querySelector("[data-language]")?.attributes["data-language"];
+
+if (!language) {
+	throw new Error(`[WranglerConfig] Unable to find data-language.`);
+}
+
+let toml, json;
+
+if (language === "toml") {
+	toml = code;
+	json = JSON.stringify(TOML.parse(code), null, 2);
+} else {
+	json = code;
+	toml = TOML.stringify(jsoncParse(code));
+}
+---
+
+<Tabs syncKey="wranglerConfig">
+	<TabItem label="wrangler.toml" icon="setting">
+		<Code lang="toml" code={toml} />
+	</TabItem>
+	<TabItem label="wrangler.json" icon="seti:json">
+		<Code lang="jsonc" code={json} />
+	</TabItem>
+</Tabs>

src/components/WranglerConfig.astro

@@ -53,6 +53,7 @@ export { default as TroubleshootingList } from "./TroubleshootingList.astro";
 export { default as TunnelCalculator } from "./TunnelCalculator.astro";
 export { default as Type } from "./Type.astro";
 export { default as TypeScriptExample } from "./TypeScriptExample.astro";
+export { default as WranglerConfig } from "./WranglerConfig.astro";
 export { default as WorkersArchitectureDiagram } from "./WorkersArchitectureDiagram.astro";
 export { default as WorkersIsolateDiagram } from "./WorkersIsolateDiagram.astro";
 export { default as WorkerStarter } from "./WorkerStarter.astro";

src/components/index.ts

@@ -5,6 +5,10 @@ productLink: "/cloudflare-one/policies/data-loss-prevention/"
 productArea: Cloudflare One
 productAreaLink: /cloudflare-one/changelog/
 entries:
+  - publish_date: "2024-11-25"
+    title: Profile confidence levels
+    description: |-
+      DLP profiles now support setting a [confidence level](/cloudflare-one/policies/data-loss-prevention/dlp-profiles/advanced-settings/#confidence-levels) to choose how tolerant its detections are to false positives based on the context of the detection. The higher a profile's confidence level is, the less false positives will be allowed. Confidence levels include Low, Medium, or High. DLP profile confidence levels supersede [context analysis](/cloudflare-one/policies/data-loss-prevention/dlp-profiles/advanced-settings/#context-analysis).
   - publish_date: "2024-11-01"
     title: Send entire HTTP requests to a Logpush destination
     description: |-

src/content/changelogs/dlp.yaml

@@ -1,8 +1,9 @@
 ---
 pcx_content_type: reference
 title: Extended DNS error codes
+sidebar:
+  order: 4
 slug: 1.1.1.1/infrastructure/extended-dns-error-codes
-
 ---
 
 

src/content/docs/1.1.1.1/infrastructure/extended-dns-error-codes.mdx

@@ -1,8 +1,9 @@
 ---
 pcx_content_type: reference
 title: Support for IPv6-only networks
+sidebar:
+  order: 3
 slug: 1.1.1.1/infrastructure/ipv6-networks
-
 ---
 
 While network infrastructure is shifting towards IPv6-only networks, providers still need to support IPv4 addresses. Dual-stack networks are networks in which all nodes have both IPv4 and IPv6 connectivity capabilities, and can therefore understand both IPv4 and IPv6 packets.

src/content/docs/1.1.1.1/infrastructure/ipv6-networks.mdx

@@ -1,8 +1,9 @@
 ---
 pcx_content_type: reference
 title: Network operators
+sidebar:
+  order: 1
 slug: 1.1.1.1/infrastructure/network-operators
-
 ---
 
 Network operators, including Internet Service Providers (ISPs), device manufacturers, public Wi-Fi networks, municipal broadband providers, and security scanning services can use [1.1.1.1](/1.1.1.1/setup/) in place of operating their own recursive DNS infrastructure.