[CF1] CF1 docs survey

Author: deadlypants1973

src/content/docs/cloudflare-one/account-limits.mdx

@@ -5,6 +5,10 @@ sidebar:
   order: 12
 ---
 
+import { Render } from "~/components";
+
+<Render file="survey" />
+
 This page lists the default account limits for rules, applications, fields, and other features. These limits may be increased on Enterprise accounts. To request a limit increase, contact your account team.
 
 ## Access

src/content/docs/cloudflare-one/api-terraform/index.mdx

@@ -3,10 +3,11 @@ pcx_content_type: navigation
 title: API and Terraform
 sidebar:
   order: 10
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing, Render } from "~/components";
+
+<Render file="survey" />
 
 This section covers a few common use cases with the API and Terraform to manage Cloudflare Zero Trust. For more information, refer to our [API documentation](/api/) and [Terraform reference guide](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs).
 

src/content/docs/cloudflare-one/applications/casb/index.mdx

@@ -10,6 +10,8 @@ learning_center:
 
 import { GlossaryTooltip, Render } from "~/components";
 
+<Render file="survey" />
+
 :::note[Availability]
 Available for all Zero Trust users.
 

src/content/docs/cloudflare-one/applications/configure-apps/index.mdx

@@ -3,9 +3,12 @@ pcx_content_type: concept
 title: Add web applications
 sidebar:
   order: 1
-
 ---
 
+import { Render } from "~/components";
+
+<Render file="survey" />
+
 Cloudflare Access allows you to secure your web applications by acting as an identity aggregator, or proxy. You can use signals from your existing identity providers (IdPs), device posture providers, and [other rules](/cloudflare-one/policies/access/#selectors) to control who can log in to the application.
 
 ![Cloudflare Access verifies a user's identity before granting access to your application.](~/assets/images/cloudflare-one/applications/diagram-saas.jpg)
@@ -15,7 +18,8 @@ You can protect the following types of web applications:
 - [**SaaS applications**](/cloudflare-one/applications/configure-apps/saas-apps/) consist of applications your team relies on that are not hosted by your organization. Examples include Salesforce and Workday. To secure SaaS applications, you must integrate Cloudflare Access with the SaaS application's SSO configuration.
 
 - **Self-hosted applications** consist of internal applications that you host in your own environment. These can be the data center versions of tools like the Atlassian suite or applications created by your own team. Setup requirements for a self-hosted application depend on whether the application is publicly accessible on the Internet or restricted to users on a private network.
-	- [**Public hostname applications**](/cloudflare-one/applications/configure-apps/self-hosted-public-app/) are web applications that have public DNS records. Anyone on the Internet can access the application by entering the URL in their browser and authenticating through Cloudflare Access. Securing access to a public website requires a Cloudflare DNS [full setup](/dns/zone-setups/full-setup/) or [partial CNAME setup](/dns/zone-setups/partial-setup/).
-	- [**Private network applications**](/cloudflare-one/applications/non-http/self-hosted-private-app/) do not have public DNS records, meaning they are not reachable from the public Internet. To connect using a private IP or private hostname, the user's traffic must route through Cloudflare Gateway. The preferred method is to install the WARP client on the user's device, but you could also forward device traffic from a [network location](/magic-wan/) or use an agentless option such as [PAC files](/cloudflare-one/connections/connect-devices/agentless/pac-files/) or [Clientless Web Isolation](/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation/).
 
-- [**Cloudflare Dashboard SSO**](/cloudflare-one/applications/configure-apps/dash-sso-apps/) is a special type of SaaS application that manages SSO settings for the Cloudflare dashboard and has limited permissions for administrator edits.
+  - [**Public hostname applications**](/cloudflare-one/applications/configure-apps/self-hosted-public-app/) are web applications that have public DNS records. Anyone on the Internet can access the application by entering the URL in their browser and authenticating through Cloudflare Access. Securing access to a public website requires a Cloudflare DNS [full setup](/dns/zone-setups/full-setup/) or [partial CNAME setup](/dns/zone-setups/partial-setup/).
+  - [**Private network applications**](/cloudflare-one/applications/non-http/self-hosted-private-app/) do not have public DNS records, meaning they are not reachable from the public Internet. To connect using a private IP or private hostname, the user's traffic must route through Cloudflare Gateway. The preferred method is to install the WARP client on the user's device, but you could also forward device traffic from a [network location](/magic-wan/) or use an agentless option such as [PAC files](/cloudflare-one/connections/connect-devices/agentless/pac-files/) or [Clientless Web Isolation](/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation/).
+
+- [**Cloudflare Dashboard SSO**](/cloudflare-one/applications/configure-apps/dash-sso-apps/) is a special type of SaaS application that manages SSO settings for the Cloudflare dashboard and has limited permissions for administrator edits.

src/content/docs/cloudflare-one/applications/index.mdx

@@ -3,10 +3,11 @@ pcx_content_type: navigation
 title: Applications
 sidebar:
   order: 6
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing, Render } from "~/components";
+
+<Render file="survey" />
 
 Cloudflare Zero Trust can secure self-hosted and SaaS applications with Zero Trust rules.
 

src/content/docs/cloudflare-one/applications/non-http/index.mdx

@@ -5,6 +5,10 @@ sidebar:
   order: 1
 ---
 
+import { Render } from "~/components";
+
+<Render file="survey" />
+
 Cloudflare offers both client-based and clientless ways to grant secure access to non-HTTP applications.
 
 :::note

src/content/docs/cloudflare-one/changelog/access.mdx

@@ -7,7 +7,9 @@ head:
 description: Review recent changes to Cloudflare Access.
 ---
 
-import { ProductChangelog } from "~/components";
+import { ProductChangelog, Render } from "~/components";
+
+<Render file="survey" />
 
 {/* <!-- All changelog entries live in src/content/changelogs/access/. */}
 

src/content/docs/cloudflare-one/changelog/browser-isolation.mdx

@@ -7,7 +7,9 @@ head:
 description: Review recent changes to Cloudflare Browser Isolation.
 ---
 
-import { ProductChangelog } from "~/components";
+import { ProductChangelog, Render } from "~/components";
+
+<Render file="survey" />
 
 {/* <!-- All changelog entries live in src/content/changelogs/browser-isolation/. */}
 

src/content/docs/cloudflare-one/changelog/casb.mdx

@@ -7,7 +7,9 @@ head:
 description: Review recent changes to Cloudflare CASB.
 ---
 
-import { ProductChangelog } from "~/components";
+import { ProductChangelog, Render } from "~/components";
+
+<Render file="survey" />
 
 {/* <!-- All changelog entries live in src/content/changelogs/casb/. */}
 

src/content/docs/cloudflare-one/changelog/dex.mdx

@@ -7,7 +7,9 @@ head:
 description: Review recent changes to Digital Experience Monitoring.
 ---
 
-import { ProductChangelog } from "~/components";
+import { ProductChangelog, Render } from "~/components";
+
+<Render file="survey" />
 
 {/* <!-- All changelog entries live in src/content/changelogs/dex/. */}