[C4Plat] Add Render provider guide

Author: pedrosousa

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/bigcommerce.mdx

@@ -5,16 +5,18 @@ head:
   - tag: title
     content: BigCommerce | Provider guides
 description: Learn how to configure your Enterprise zone with BigCommerce.
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="provider-guide-intro" params={{ one: "BigCommerce" }} />
+<Render file="provider-guide-intro" params={{ providerName: "BigCommerce" }} />
 
 ## Benefits
 
-<Render file="provider-guide-benefits" params={{ one: "BigCommerce" }} />
+<Render
+	file="provider-guide-benefits"
+	params={{ providerName: "BigCommerce" }}
+/>
 
 ## How it works
 
@@ -32,12 +34,10 @@ To enable O2O on your account, [create](/dns/manage-dns-records/how-to/create-dn
 
 :::note
 
-
 For more details about a BigCommerce setup, refer to their [support guide](https://support.bigcommerce.com/s/article/Cloudflare-for-Performance-and-Security?language=en_US#orange-to-orange).
 
 If you cannot activate your domain using [proxied DNS records](/dns/proxy-status/), reach out to your account team.
 
-
 :::
 
 ## Product compatibility
@@ -46,4 +46,4 @@ If you cannot activate your domain using [proxied DNS records](/dns/proxy-status
 
 ## Additional support
 
-<Render file="provider-guide-help" params={{ one: "BigCommerce" }} />
+<Render file="provider-guide-help" params={{ providerName: "BigCommerce" }} />

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/hubspot.mdx

@@ -5,16 +5,15 @@ head:
   - tag: title
     content: HubSpot | Provider guides
 description: Learn how to configure your zone with HubSpot.
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="provider-guide-intro" params={{ one: "HubSpot" }} />
+<Render file="provider-guide-intro" params={{ providerName: "HubSpot" }} />
 
 ## Benefits
 
-<Render file="provider-guide-benefits" params={{ one: "HubSpot" }} />
+<Render file="provider-guide-benefits" params={{ providerName: "HubSpot" }} />
 
 ## How it works
 
@@ -30,10 +29,8 @@ O2O is enabled per hostname, so to enable O2O for a specific hostname within you
 
 :::note
 
-
 For questions about your HubSpot setup, refer to [HubSpot's reverse proxy support guide](https://developers.hubspot.com/docs/cms/developer-reference/reverse-proxy-support).
 
-
 :::
 
 ## Product compatibility
@@ -50,4 +47,4 @@ Once the zone hold is temporarily disabled, follow HubSpot's instructions to ref
 
 ## Additional support
 
-<Render file="provider-guide-help" params={{ one: "HubSpot" }} />
+<Render file="provider-guide-help" params={{ providerName: "HubSpot" }} />

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/kinsta.mdx

@@ -5,16 +5,15 @@ head:
   - tag: title
     content: Kinsta | Provider guides
 description: Learn how to configure your Enterprise zone with Kinsta.
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="provider-guide-intro" params={{ one: "Kinsta" }} />
+<Render file="provider-guide-intro" params={{ providerName: "Kinsta" }} />
 
 ## Benefits
 
-<Render file="provider-guide-benefits" params={{ one: "Kinsta" }} />
+<Render file="provider-guide-benefits" params={{ providerName: "Kinsta" }} />
 
 ## How it works
 
@@ -36,7 +35,7 @@ To enable O2O for a specific hostname within a Cloudflare zone, [create](/dns/ma
 
 ## Additional support
 
-<Render file="provider-guide-help" params={{ one: "Kinsta" }} />
+<Render file="provider-guide-help" params={{ providerName: "Kinsta" }} />
 
 ### Resolving SSL errors using Cloudflare Managed Certificates
 

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/render.mdx

@@ -0,0 +1,70 @@
+---
+pcx_content_type: configuration
+title: Render
+head:
+  - tag: title
+    content: Render | Provider guides
+description: Learn how to configure your Enterprise zone with Render.
+---
+
+import { Render } from "~/components";
+
+<Render
+	file="provider-guide-intro"
+	params={{
+		providerName: "Render",
+		providerUrl: "https://render.com",
+		providerAssets: "web services and static sites",
+	}}
+/>
+
+## Benefits
+
+<Render
+	file="provider-guide-benefits"
+	params={{ providerName: "Render", providerAssets: "services" }}
+/>
+
+## How it works
+
+For additional detail about how traffic routes when O2O is enabled, refer to [How O2O works](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/).
+
+## Enable
+
+Render customers can enable O2O on any Cloudflare zone plan. Cloudflare support for O2O setups is only available for Enterprise customers.
+
+To enable O2O for a specific hostname within a Cloudflare zone, [create](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records) a Proxied `CNAME` DNS record with your Render site name as the target. Render's domain addition setup will walk you through other validation steps.
+
+| Type    | Name              | Target                                                     | Proxy status |
+| ------- | ----------------- | ---------------------------------------------------------- | ------------ |
+| `CNAME` | `<YOUR_HOSTNAME>` | `<RENDER_SUBDOMAIN>` (for example, `example.onrender.com`) | Proxied      |
+
+:::note
+
+For more details about Render setup, refer to their [documentation](https://render.com/docs/configure-cloudflare-dns).
+
+If you cannot activate your domain using [proxied DNS records](/dns/proxy-status/), reach out to your Cloudflare account team or your Render support team.
+
+:::
+
+### Additional requirements for wildcard subdomains
+
+With O2O enabled, adding a wildcard subdomain to a Render service requires that the corresponding root domain is also routed to Render. If the root domain is routed elsewhere, wildcard routing will fail.
+
+If your root domain needs to route somewhere besides Render, add individual subdomains to your Render service instead of a wildcard.
+
+## Product compatibility
+
+<Render file="provider-guide-compatibility" />
+
+## Additional support
+
+<Render file="provider-guide-help" params={{ providerName: "Render" }} />
+
+### Resolving SSL errors
+
+If you encounter SSL errors, check if you have a `CAA` record.
+
+If you have a `CAA` record, verify that it permits SSL certificates to be issued by Google Trust Services (`pki.goog`).
+
+For more details, refer to [CAA records](/ssl/edge-certificates/troubleshooting/caa-records/#what-caa-records-are-added-by-cloudflare).

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/salesforce-commerce-cloud.mdx

@@ -11,14 +11,14 @@ import { Details, Render } from "~/components";
 
 <Render
 	file="provider-guide-intro"
-	params={{ one: "Salesforce Commerce Cloud" }}
+	params={{ providerName: "Salesforce Commerce Cloud" }}
 />
 
 ## Benefits
 
 <Render
 	file="provider-guide-benefits"
-	params={{ one: "Salesforce Commerce Cloud" }}
+	params={{ providerName: "Salesforce Commerce Cloud" }}
 />
 
 ## How it works
@@ -30,8 +30,8 @@ For additional detail about how traffic routes when O2O is enabled, refer to [Ho
 To enable O2O requires the following:
 
 1. You must configure your SFCC environment as an "SFCC Proxy Zone". If you currently have an "SFCC Legacy Zone", you cannot enable O2O.
-    - For more details on the different types of SFCC configurations, refer to the [Salesforce FAQ on SFCC Proxy Zones](https://help.salesforce.com/s/articleView?id=cc.b2c_ecdn_proxy_zone_faq.htm&type=5).
-    - For instructions on how to migrate your SFCC environment to an "SFCC Proxy Zone", refer to the [SFCC Legacy Zone to SFCC Proxy Zone migration guide](https://help.salesforce.com/s/articleView?id=cc.b2c_migrate_legacy_zone_to_proxy_zone.htm&type=5).
+   - For more details on the different types of SFCC configurations, refer to the [Salesforce FAQ on SFCC Proxy Zones](https://help.salesforce.com/s/articleView?id=cc.b2c_ecdn_proxy_zone_faq.htm&type=5).
+   - For instructions on how to migrate your SFCC environment to an "SFCC Proxy Zone", refer to the [SFCC Legacy Zone to SFCC Proxy Zone migration guide](https://help.salesforce.com/s/articleView?id=cc.b2c_migrate_legacy_zone_to_proxy_zone.htm&type=5).
 2. Your own Cloudflare zone on an Enterprise plan.
 
 If you meet the above requirements, O2O can then be enabled per hostname. To enable O2O for a specific hostname within your Cloudflare zone, [create](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records) a Proxied CNAME DNS record with a target of the CNAME provided by SFCC Business Manager, which is the dashboard used by SFCC customers to configure their storefront environment.
@@ -78,7 +78,7 @@ And, the following is an **incorrect** configuration because `preview.example.co
 
 <Render
 	file="provider-guide-help"
-	params={{ one: "Salesforce Commerce Cloud" }}
+	params={{ providerName: "Salesforce Commerce Cloud" }}
 />
 
 ### Resolving SSL errors using Cloudflare Managed Certificates

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/shopify.mdx

@@ -9,7 +9,7 @@ description: Learn how to configure your zone with Shopify.
 
 import { Render } from "~/components";
 
-<Render file="provider-guide-intro" params={{ one: "Shopify" }} />
+<Render file="provider-guide-intro" params={{ providerName: "Shopify" }} />
 
 ## Benefits
 
@@ -51,7 +51,7 @@ If you cannot activate your domain using [proxied DNS records](/dns/proxy-status
 
 ## Additional support
 
-<Render file="provider-guide-help" params={{ one: "Shopify" }} />
+<Render file="provider-guide-help" params={{ providerName: "Shopify" }} />
 
 ### DNS CAA records
 

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/wpengine.mdx

@@ -5,16 +5,15 @@ head:
   - tag: title
     content: WP Engine | Provider guides
 description: Learn how to configure your zone with WP Engine.
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
-<Render file="provider-guide-intro" params={{ one: "WP Engine" }} />
+<Render file="provider-guide-intro" params={{ providerName: "WP Engine" }} />
 
 ## Benefits
 
-<Render file="provider-guide-benefits" params={{ one: "WP Engine" }} />
+<Render file="provider-guide-benefits" params={{ providerName: "WP Engine" }} />
 
 ## How it works
 
@@ -32,12 +31,10 @@ To enable O2O for a specific hostname within a Cloudflare zone, [create](/dns/ma
 
 :::note
 
-
 For questions about WP Engine setup, refer to their [support guide](https://wpengine.com/support/wordpress-best-practice-configuring-dns-for-wp-engine/#Point_DNS_Using_CNAME_Flattening).
 
 If you cannot activate your domain using [proxied DNS records](/dns/proxy-status/), reach out to your account team.
 
-
 :::
 
 ## Product compatibility
@@ -54,7 +51,7 @@ Once the zone hold is temporarily disabled, follow WP Engine's instructions to r
 
 ## Additional support
 
-<Render file="provider-guide-help" params={{ one: "WP Engine" }} />
+<Render file="provider-guide-help" params={{ providerName: "WP Engine" }} />
 
 ### Resolving SSL errors
 

src/content/partials/cloudflare-for-platforms/provider-guide-benefits.mdx

@@ -1,8 +1,9 @@
 ---
-inputParameters: providerName
-
+params:
+  - providerName
+  - providerAssets?
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
-O2O's benefits include applying your own Cloudflare zone's services and settings - such as [WAF](/waf/), [Bot Management](/bots/plans/bm-subscription/), [Waiting Room](/waiting-room/), and more - on the traffic destined for your {props.one} environment.
+O2O's benefits include applying your own Cloudflare zone's services and settings — such as [WAF](/waf/), [Bot Management](/bots/plans/bm-subscription/), [Waiting Room](/waiting-room/), and more — on the traffic destined for your {props.providerName} {props.providerAssets ?? "environment" }.

src/content/partials/cloudflare-for-platforms/provider-guide-help.mdx

@@ -1,10 +1,10 @@
 ---
-inputParameters: providerName
-
+params:
+  - providerName
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
-If you are a {props.one} customer and have set up your own Cloudflare zone with O2O enabled on specific hostnames, contact your Cloudflare Account Team or [Cloudflare Support](/support/contacting-cloudflare-support/) for help resolving issues in your own zone.
+If you are a {props.providerName} customer and have set up your own Cloudflare zone with O2O enabled on specific hostnames, contact your Cloudflare Account Team or [Cloudflare Support](/support/contacting-cloudflare-support/) for help resolving issues in your own zone.
 
-Cloudflare will turn to {props.one} if there are technical issues that Cloudflare cannot resolve.
+Cloudflare will consult {props.providerName} if there are technical issues that Cloudflare cannot resolve.

src/content/partials/cloudflare-for-platforms/provider-guide-intro.mdx

@@ -1,10 +1,12 @@
 ---
-inputParameters: providerName
-
+params:
+  - providerName
+  - providerUrl?
+  - providerAssets?
 ---
 
-import { Markdown } from "~/components"
+import { Markdown } from "~/components";
 
-Cloudflare partners with {props.one} to provide {props.one} customers’ websites with Cloudflare’s performance and security benefits.
+Cloudflare partners with { props.providerUrl ? <Markdown text={`[${props.providerName}](${props.providerUrl})`} inline={true} /> : props.providerName } to provide {props.providerName} customers’ {props.providerAssets ?? "websites"} with Cloudflare’s performance and security benefits.
 
-If you use {props.one} and also have a Cloudflare plan, you can use your own Cloudflare zone to proxy web traffic to your zone first, then {props.one}'s (the SaaS Provider) zone second. This configuration option is called [Orange-to-Orange (O2O)](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/).
+If you use {props.providerName} and also have a Cloudflare plan, you can use your own Cloudflare zone to proxy web traffic to your zone first, then {props.providerName}'s (the SaaS Provider) zone second. This configuration option is called [Orange-to-Orange (O2O)](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/).