[SaaS] Add #zone-hold callout to all provider guides (#26141)

* Create provider-guide-zone-hold and apply to webflow.mdx

* Auto-apply partial to all provider guides

Author: RebeccaTamachiro

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

@@ -52,6 +52,14 @@ If you cannot activate your domain using [proxied DNS records](/dns/proxy-status
 	product="cloudflare-for-platforms"
 />
 
+## Zone hold
+
+<Render
+	file="provider-guide-zone-hold"
+	params={{ providerName: "BigCommerce" }}
+	product="cloudflare-for-platforms"
+/>
+
 ## Additional support
 
 <Render

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

@@ -50,11 +50,11 @@ For questions about your HubSpot setup, refer to [HubSpot's reverse proxy suppor
 
 ## Zone hold
 
-Because you have your own Cloudflare zone, you have access to the zone hold feature, which is a toggle that prevents your domain name from being created as a zone in a different Cloudflare account. Additionally, if the zone hold feature is enabled, it prevents the activation of custom hostnames onboarded to HubSpot. HubSpot would receive the following error message for your custom hostname: `The hostname is associated with a held zone. Please contact the owner of this domain to have the hold removed.`
-
-To successfully activate the custom hostname on HubSpot, the owner of the zone needs to [temporarily release the hold](/fundamentals/account/account-security/zone-holds/#release-zone-holds). If you are only onboarding a subdomain as a custom hostname to HubSpot, only the subfeature titled `Also prevent Subdomains` needs to be temporarily disabled.
-
-Once the zone hold is temporarily disabled, follow HubSpot's instructions to refresh the custom hostname and it should activate.
+<Render
+	file="provider-guide-zone-hold"
+	params={{ providerName: "HubSpot" }}
+	product="cloudflare-for-platforms"
+/>
 
 ## Additional support
 

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

@@ -44,6 +44,14 @@ To enable O2O for a specific hostname within a Cloudflare zone, [create](/dns/ma
 	product="cloudflare-for-platforms"
 />
 
+## Zone hold
+
+<Render
+	file="provider-guide-zone-hold"
+	params={{ providerName: "Kinsta" }}
+	product="cloudflare-for-platforms"
+/>
+
 ## Additional support
 
 <Render

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

@@ -62,6 +62,14 @@ If your root domain needs to route somewhere besides Render, add individual subd
 	product="cloudflare-for-platforms"
 />
 
+## Zone hold
+
+<Render
+	file="provider-guide-zone-hold"
+	params={{ providerName: "Render" }}
+	product="cloudflare-for-platforms"
+/>
+
 ## Additional support
 
 <Render

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

@@ -79,6 +79,14 @@ And, the following is an **incorrect** configuration because `preview.example.co
 	product="cloudflare-for-platforms"
 />
 
+## Zone hold
+
+<Render
+	file="provider-guide-zone-hold"
+	params={{ providerName: "Salesforce Commerce Cloud" }}
+	product="cloudflare-for-platforms"
+/>
+
 ## Additional support
 
 <Render

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

@@ -56,6 +56,14 @@ If you cannot activate your domain using [proxied DNS records](/dns/proxy-status
 	product="cloudflare-for-platforms"
 />
 
+## Zone hold
+
+<Render
+	file="provider-guide-zone-hold"
+	params={{ providerName: "Shopify" }}
+	product="cloudflare-for-platforms"
+/>
+
 ## Additional support
 
 <Render

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

@@ -33,6 +33,14 @@ To enable O2O for a specific hostname within a Cloudflare Zone, [create](/dns/ma
 | ------- | -------------------- | --------------------- | ------------ |
 | `CNAME` | `<YOUR_DOMAIN>`      | `cdn.webflow.com`     | Proxied      |
 
+## Zone hold
+
+<Render
+	file="provider-guide-zone-hold"
+	params={{ providerName: "Webflow" }}
+	product="cloudflare-for-platforms"
+/>
+
 ## Product compatibility
 
 <Render

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

@@ -54,11 +54,11 @@ If you cannot activate your domain using [proxied DNS records](/dns/proxy-status
 
 ## Zone hold
 
-If your own Cloudflare zone is on the Enterprise plan, you have access to the [zone hold feature](/fundamentals/account/account-security/zone-holds/), which is a toggle that prevents your domain name from being created as a zone in a different Cloudflare account. Additionally, if the zone hold is enabled, it prevents the activation of custom hostnames onboarded to WP Engine. WP Engine would receive the following error message for your custom hostname: `The hostname is associated with a held zone. Please contact the owner of this domain to have the hold removed.`
-
-To successfully activate the custom hostname on WP Engine, the owner of the zone needs to [temporarily release the hold](/fundamentals/account/account-security/zone-holds/#release-zone-holds). If you are only onboarding a subdomain as a custom hostname to WP Engine, only the subfeature titled `Also prevent Subdomains` needs to be temporarily disabled.
-
-Once the zone hold is temporarily disabled, follow WP Engine's instructions to refresh the custom hostname and it should activate.
+<Render
+	file="provider-guide-zone-hold"
+	params={{ providerName: "WP Engine" }}
+	product="cloudflare-for-platforms"
+/>
 
 ## Additional support
 

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

@@ -0,0 +1,12 @@
+---
+params:
+  - providerName
+---
+
+import { Markdown } from "~/components";
+
+If your own Cloudflare zone is on the Enterprise plan, you have access to the [zone hold feature](/fundamentals/account/account-security/zone-holds/), which is a toggle that prevents your domain name from being created as a zone in a different Cloudflare account. Additionally, if the zone hold is enabled, it prevents the activation of custom hostnames onboarded to {props.providerName}. {props.providerName} would receive the following error message for your custom hostname: `The hostname is associated with a held zone. Please contact the owner of this domain to have the hold removed.`
+
+To successfully activate the custom hostname on {props.providerName}, the owner of the zone needs to [temporarily release the hold](/fundamentals/account/account-security/zone-holds/#release-zone-holds). If you are only onboarding a subdomain as a custom hostname to {props.providerName}, only the subfeature titled **Also prevent Subdomains** needs to be temporarily disabled.
+
+Once the zone hold is temporarily disabled, follow {props.providerName}'s instructions to refresh the custom hostname and it should activate.