Merge branch 'production' into penalosa/wrangler-config-component

Author: penalosa

package-lock.json

@@ -38,7 +38,7 @@
 		"@cloudflare/vitest-pool-workers": "^0.5.31",
 		"@cloudflare/workers-types": "^4.20241112.0",
 		"@codingheads/sticky-header": "^1.0.2",
-		"@iconify-json/material-symbols": "^1.2.7",
+		"@iconify-json/material-symbols": "^1.2.8",
 		"@iarna/toml": "^2.2.5",
 		"@stoplight/json-schema-tree": "^4.0.0",
 		"@types/dompurify": "^3.2.0",
@@ -64,7 +64,7 @@
 		"instantsearch.js": "^4.75.4",
 		"jsonc-parser": "^3.3.1",
 		"lz-string": "^1.5.0",
-		"marked": "^14.1.3",
+		"marked": "^15.0.2",
 		"mdast-util-mdx-expression": "^2.0.1",
 		"mermaid": "^11.4.0",
 		"node-html-parser": "^6.1.13",

package.json

@@ -13,7 +13,9 @@ Enable and customize your gateway cache to serve requests directly from Cloudfla
 
 :::note
 
-Currently caching is supported only for text and image responses, and it applies only to identical requests. This is helpful for use cases when there are limited prompt options - for example, a support bot that asks "How can I help you?" and lets the user select an answer from a limited set of options works well with the current caching configuration.
+Currently caching is supported only for text and image responses, and it applies only to identical requests. 
+
+This is helpful for use cases when there are limited prompt options - for example, a support bot that asks "How can I help you?" and lets the user select an answer from a limited set of options works well with the current caching configuration.
 We plan on adding semantic search for caching in the future to improve cache hit rates.
 :::
 

src/content/docs/ai-gateway/configuration/caching.mdx

@@ -58,7 +58,7 @@ Drizzle is a headless TypeScript ORM with a head which runs on Node, Bun and Den
 
 * [Docs](https://orm.drizzle.team/docs)
 * [GitHub](https://github.com/drizzle-team/drizzle-orm)
-* [D1 example](https://orm.drizzle.team/docs/get-started-sqlite#cloudflare-d1)
+* [D1 example](https://orm.drizzle.team/docs/connect-cloudflare-d1)
 
 ### Flyweight
 

src/content/docs/d1/reference/community-projects.mdx

@@ -23,6 +23,8 @@ A single DDoS attack consisting of thousands of bots can involve as little as on
 
 In the case of HTTPS DDoS attacks, service providers only see encrypted payloads leaving their network without any possibility to decrypt or understand if it is malicious or legitimate traffic. However, Cloudflare can see an entire attack and all of its sources if the attack targets an Internet property that uses Cloudflare's services. This global view can help service providers stop the abusers.
 
+For more details, refer to [How DDoS protection works](/ddos-protection/about/how-ddos-protection-works/).
+
 ## Availability
 
 The Cloudflare DDoS Botnet Threat Feed is available for free to service providers. For more information, refer to the [Terms of Use](https://www.cloudflare.com/en-gb/service-specific-terms-application-services/#ddos-botnet-threat-feed).
@@ -45,6 +47,10 @@ Make sure that:
 4. On the list of ASNs configured for your threat feed, select **Add ASN**.
 5. You will be redirected to the PeeringDB authentication page, where you can log in and consent to share the affiliation data with us. You will be redirected back to the configuration page once it is successful.
 
+:::note
+You can add multiple ASNs to your threat feed.
+:::
+
 ### 2. Obtain Cloudflare API token
 
 You must [obtain a Cloudflare API token](/fundamentals/api/get-started/create-token/) with at least the following account-level permission:
@@ -66,6 +72,7 @@ Invoke one of the Botnet Threat Feed API endpoints:
 
 - The API URI path is planned to change from `.../botnet_feed/...` to `.../ddos_botnet_feed/...` in the future.
 - Responses with no IP addresses in the results (empty state) will return an `HTTP 200` status code (success), with an empty list in the `result` property.
+- When the response is a success but the result is `0` or `null`, this means that there are no detected offenses.
 :::
 
 To invoke an API endpoint, append the operation endpoint to the Cloudflare API base URL:

src/content/docs/ddos-protection/botnet-threat-feed.mdx

@@ -13,6 +13,20 @@ Applications are currently open until Thursday, the 24th of October 2024. To app
 
 ## View latest contributions
 
+<LinkTitleCard
+	title="Build an interview practice tool with Workers AI"
+	href="/workers-ai/tutorials/build-ai-interview-practice-tool/"
+>
+	By Vasyl
+</LinkTitleCard>
+
+<LinkTitleCard
+	title="Automate analytics reporting with Cloudflare Workers and email routing"
+	href="/workers/tutorials/automated-analytics-reporting/"
+>
+	By Aleksej Komnenovic
+</LinkTitleCard>
+
 <LinkTitleCard
 	title="Create a sitemap from Sanity CMS with Workers"
 	href="/developer-spotlight/tutorials/create-sitemap-from-sanity-cms/"

src/content/docs/developer-spotlight/index.mdx

@@ -6,13 +6,10 @@ title: Move a domain between Cloudflare accounts
 
 You will have to move or transfer domains from one Cloudflare account to another if you:
 
-* Manage a multi-user organization and need to segment domain access by user.
-
-* Receive a `Cloudflare is already hosting under a different account` error.
-
-* Lose access to your email address or Cloudflare account (though you can also use the [backup codes](/fundamentals/setup/account/account-security/2fa/#use-a-backup-code) if you have two-factor authentication enabled).
-
-* Registered a Cloudflare account with a typo in your email.
+- Manage a multi-user organization and need to segment domain access by user.
+- Receive a `Cloudflare is already hosting under a different account` error.
+- Lose access to your email address or Cloudflare account (though you can also use the [backup codes](/fundamentals/setup/account/account-security/2fa/#use-a-backup-code) if you have two-factor authentication enabled).
+- Registered a Cloudflare account with a typo in your email.
 
 :::caution
 If your domain is registered with Cloudflare Registrar, you need to submit a manual request to transfer the domain and its registration to a new account.
@@ -24,8 +21,8 @@ Refer to [Transfer a Cloudflare Registrar domain registration between accounts](
 
 To transfer a domain from one Cloudflare account to another, you will need:
 
-* Access to your domain registrar. If your domain is using Cloudflare Registrar, you will need to refer to [Transfer a Cloudflare Registrar domain registration between accounts](/registrar/account-options/inter-account-transfer/).
-* At least one Cloudflare account associated with the domain.
+- Access to your domain registrar. If your domain is using Cloudflare Registrar, refer to [Transfer a Cloudflare Registrar domain registration between accounts](/registrar/account-options/inter-account-transfer/).
+- At least one Cloudflare account associated with the domain.
 
 ## Transfer your domain
 
@@ -40,18 +37,15 @@ If you miss this step, Cloudflare will import your proxied DNS records, which mi
 
 :::
 
-If you still have access to your previous Cloudflare account, you can copy over the Cloudflare account settings manually. You must reissue [SSL/TLS certificates](/ssl/edge-certificates/) and [recreate and validate DNS records](/dns/manage-dns-records/how-to/create-dns-records/) when transferring domains between Cloudflare accounts.
+If you still have access to your previous Cloudflare account, you can copy over the Cloudflare account settings manually. You must reissue [SSL/TLS certificates](#issue-new-certificates) and [recreate and validate DNS records](/dns/manage-dns-records/how-to/create-dns-records/) when transferring domains between Cloudflare accounts.
 
 If you lose access to the email address associated with your Cloudflare account and do not have backup codes, you will need to manually transfer your domain to a new Cloudflare account associated with a different email address.
 
 The domain transfer process depends on your DNS settings. If Cloudflare is your authoritative DNS provider (that is, your domain nameservers point to Cloudflare), you must:
 
 1. [Create a new Cloudflare account](/fundamentals/setup/account/create-account/) or log in to an existing Cloudflare account.
-
 2. [Add the domain](/fundamentals/setup/manage-domains/add-site/) to the account (as if you were adding it for the first time).
-
 3. Log in to your domain registrar account and [update the nameservers](/dns/zone-setups/full-setup/setup/) to the provided Cloudflare nameservers.
-
 4. Finalize the nameserver update by selecting your domain in the dashboard > **Overview** > **Re-check now**.
 
 Once the Cloudflare network recognizes the nameserver change, the domain in the new account will be marked as **Active**. While the domain in the new account is **Pending**, it cannot proxy traffic through Cloudflare and the origin IP addresses will be returned until the domain is marked as **Active**.
@@ -64,7 +58,6 @@ For more information, refer to [Zone status](/dns/zone-setups/reference/domain-s
 
 SSL/TLS certificates associated with your previous Cloudflare account will not be transferred to your new account. If your site requires an SSL/TLS certificate prior to domain transfer, refer to [Minimize downtime](/ssl/edge-certificates/universal-ssl/enable-universal-ssl/#minimize-downtime).
 
-If you were using [Custom certificates](/ssl/edge-certificates/custom-certificates/), you will need to delete them from the previous zone and upload them to the new zone.
-You can upload them whilst the new zone is pending: they will have the [Holding Deployment](/ssl/reference/certificate-statuses/#custom-certificates) status and will become active once the zone is active.
+If you were using [custom certificates](/ssl/edge-certificates/custom-certificates/), you will need to delete them from the previous zone and upload them to the new zone. You can upload the certificates while the new zone is in **Pending** status - if you do so, once you upload the certificates, they will have a [**Holding Deployment**](/ssl/reference/certificate-statuses/#custom-certificates) status and will become active once the zone is active.
 
-You can order an [advanced certificate](/ssl/edge-certificates/advanced-certificate-manager/) prior to transferring your domain. Once issued, the certificate will enter **Holding Deployment** status until the domain is active. ACM certificates will automatically deploy to active domains. For more information, refer to [Custom certificates](/ssl/reference/certificate-statuses/#custom-certificates).
+You can order an [advanced certificate](/ssl/edge-certificates/advanced-certificate-manager/) prior to transferring your domain. ACM certificates will automatically deploy to active domains.