[Challenges] Address feedback to the new tile (#22312)

* remove plan type

* references order

* troubleshooting order

* language support

* move JSD from Bots to Challenges

* broken partial

* broken partial pt 2

* update codeowners

Author: patriciasantaana

.github/CODEOWNERS

@@ -212,6 +212,7 @@
 /src/content/docs/waf/ @pedrosousa @cloudflare/firewall @cloudflare/pcx-technical-writing
 /src/content/docs/waf/change-log/ @pedrosousa @cloudflare/firewall @vs-mg @cloudflare/pcx-technical-writing
 /src/content/release-notes/waf.yaml @pedrosousa @cloudflare/firewall @vs-mg @cloudflare/pcx-technical-writing
+/src/content/docs/cloudflare-challenges/ @patriciasantaana @cloudflare/pcx-technical-writing
 
 # Support
 

public/__redirects

@@ -233,6 +233,7 @@
 /bots/get-started/free/ /bots/get-started/bot-fight-mode/ 301
 /bots/get-started/bm-subscription/ /bots/get-started/bot-management/ 301
 /bots/get-started/pro/ /bots/get-started/super-bot-fight-mode/ 301
+/bots/additional-configurations/javascript-detections/ /cloudflare-challenges/challenge-types/javascript-detections/ 301
 
 #browser-rendering
 /browser-rendering/get-started/browser-rendering-with-do/ /browser-rendering/workers-binding-api/browser-rendering-with-do/ 301

src/content/docs/bots/additional-configurations/javascript-detections.mdx

@@ -1,46 +1,7 @@
 ---
-type: overview
-pcx_content_type: reference
+pcx_content_type: concept
 title: JavaScript detections
+external_link: /cloudflare-challenges/challenge-types/javascript-detections/
 sidebar:
-  order: 6
----
-
-import { Render } from "~/components"
-
-<Render file="javascript-detections-definition" params={{ one: " " }} />
-
-## Enable JavaScript detections
-
-For Free customers (Bot Fight Mode), JavaScript detections are automatically enabled and cannot be disabled.
-
-For all other customers (Super Bot Fight Mode and Bot Management for Enterprise), JavaScript detections are optional.
-
-<Render file="javascript-detections-enable" />
-
-For more details on how to set up bot protection, see [Get started](/bots/get-started/).
-
-## Enforcing execution of JavaScript detections
-
-<Render file="javascript-detections-implementation" />
-
-<Render file="cf-clearance-cookie" />
-
-## Limitations
-
-### If you enabled Bot Management before June 2020
-
-Customers who enabled Enterprise Bot Management before June 2020 do not have JavaScript detections enabled by default (unless specifically requested). These customers can still enable the feature in the Cloudflare dashboard.
-
-### If you have a Content Security Policy (CSP)
-
-<Render file="javascript-detections-csp" />
-
-:::caution[Warning]
-
-JavaScript detections are not supported with `nonce` set via `<meta>` tags. 
-:::
-
-### If you have ETags
-
-Enabling JavaScript Detections (JSD) will strip [ETags](/cache/reference/etag-headers/) from HTML responses where JSD is injected.
+  order: 2
+---

src/content/docs/bots/get-started/bot-management.mdx

@@ -51,7 +51,7 @@ You can view blocked AI bot traffic via [Security Analytics](/waf/analytics/secu
 
 Enabling [JavaScript detections](/bots/additional-configurations/javascript-detections/) validates that the browser can run JavaScript, and is stored in the `cf.bot_management.js_detection.passed` variable.
 
-<Render file="javascript-detections-enable" params={{ one: "Bot Management" }} />
+<Render file="javascript-detections-enable" params={{ one: "Bot Management" }} product="cloudflare-challenges" />
 
 ### Deploy default templates
 

src/content/docs/cloudflare-challenges/challenge-types/javascript-detections.mdx

@@ -1,7 +1,47 @@
+
 ---
-pcx_content_type: concept
+type: overview
+pcx_content_type: reference
 title: JavaScript detections
-external_link: /bots/additional-configurations/javascript-detections/
 sidebar:
-  order: 2
----
+  order: 6
+---
+
+import { Render } from "~/components"
+
+<Render file="javascript-detections-definition" />
+
+## Enable JavaScript detections
+
+For Bot Fight Mode customers, JavaScript detections are automatically enabled and cannot be disabled.
+
+For Super Bot Fight Mode and Bot Management for Enterprise customers, JavaScript detections are optional.
+
+<Render file="javascript-detections-enable" />
+
+For more details on how to set up bot protection, refer to the [Bots documentation](/bots/get-started/).
+
+## Enforcing execution of JavaScript detections
+
+<Render file="javascript-detections-implementation" />
+
+<Render file="cf-clearance-cookie" />
+
+## Limitations
+
+### If you enabled Bot Management before June 2020
+
+Customers who enabled Enterprise Bot Management before June 2020 do not have JavaScript detections enabled by default (unless specifically requested). These customers can still enable the feature in the Cloudflare dashboard.
+
+### If you have a Content Security Policy (CSP)
+
+<Render file="javascript-detections-csp" />
+
+:::caution[Warning]
+
+JavaScript detections are not supported with `nonce` set via `<meta>` tags. 
+:::
+
+### If you have ETags
+
+Enabling JavaScript Detections (JSD) will strip [ETags](/cache/reference/etag-headers/) from HTML responses where JSD is injected.

src/content/docs/cloudflare-challenges/index.mdx

@@ -11,8 +11,6 @@ import { Render, Description, Plan, RelatedProduct } from "~/components";
 Challenges are security mechanisms used by Cloudflare to verify whether a visitor to your site is a real human and not a bot or automated script. 
 </Description>
 
-<Plan type="all" />
-
 When a challenge is issued, Cloudflare asks the browser to perform a series of checks that help confirm the visitor’s legitimacy. This process involves evaluating client side signals or asking a visitor to take minimal action such as checking a box. Challenges are designed to protect your application without introducing unnecessary friction. Most visitors will pass challenges automatically without interaction. 
 
 Cloudflare does not use CAPTCHA puzzles or visual tests like selecting objects or typing distorted characters. All challenge types are lightweight, privacy-preserving, and optimized for real-world traffic. 

src/content/docs/cloudflare-challenges/reference/challenge-solve-rate.mdx

@@ -2,7 +2,7 @@
 pcx_content_type: reference
 title: Challenge solve rate (CSR)
 sidebar:
-  order: 1
+  order: 2
 ---
 
 import { Render } from "~/components"

src/content/docs/cloudflare-challenges/reference/private-access-tokens.mdx

@@ -2,7 +2,7 @@
 pcx_content_type: reference
 title: Private Access Tokens (PAT)
 sidebar:
-  order: 4
+  order: 3
 ---
 
 When a user is presented with a challenge page, Cloudflare decides what challenges need to be solved to prove they are human using results from the Private Access Token (PAT). If a user presents a token, they will have an easier time solving the challenge.

src/content/docs/cloudflare-challenges/reference/supported-browsers.mdx

@@ -2,7 +2,7 @@
 pcx_content_type: reference
 title: Supported browsers
 sidebar:
-  order: 2
+  order: 4
 ---
 
 When your application sends a challenge, your visitors either receive a non-interactive or an interactive challenge page.

src/content/docs/cloudflare-challenges/reference/supported-languages.mdx

@@ -9,7 +9,7 @@ sidebar:
 
 Cloudflare's challenges can detect multiple languages and display the localized challenge experience, which is determined by `navigator.language` value. The [Navigator.language read-only property](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/language) returns a string representing the preferred language of the user, usually the language of the browser user interface. 
 
-Refer to the table below for currently supported languages.
+For language support specific to challenge pages, refer to the table below. 
 
 | Language                         | Language code<br/>(4 letters) | Language code<br/>(2 letters) |
 | -------------------------------- | ----------------------------- | ----------------------------- |