Skip to content

Commit 2513adc

Browse files
mia303dcpena
authored andcommitted
Adding Webflow provider guide to Cloudflare for SaaS docs (#24608)
* added-provider-guide-content * Update src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/webflow.mdx Co-authored-by: Denise Peña <[email protected]> --------- Co-authored-by: Denise Peña <[email protected]>
1 parent 4d3bbe9 commit 2513adc

File tree

1 file changed

+47
-0
lines changed
  • src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides

1 file changed

+47
-0
lines changed
Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
---
2+
pcx_content_type: configuration
3+
title: Webflow
4+
head:
5+
- tag: title
6+
content: Webflow | Provider guides
7+
description: Learn how to configure your Enterprise zone with Webflow.
8+
---
9+
10+
import { Render } from "~/components";
11+
12+
<Render file="provider-guide-intro" params={{ providerName: "Webflow" }} />
13+
14+
## Benefits
15+
16+
O2O's benefits include applying your own Cloudflare zone's services and settings — such as WAF, Bot Management, Waiting Room, and more — on the traffic destined for your Webflow environment.
17+
18+
## How it works
19+
20+
For more details about how O2O is different than other Cloudflare setups, refer to [How O2O works](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/).
21+
22+
## Enable
23+
24+
You can enable O2O on any Cloudflare zone plan.
25+
26+
To enable O2O on your account, [create](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records) a `CNAME` DNS record.
27+
28+
| Type | Name | Target | Proxy status |
29+
| ------- | -------------------- | --------------------- | ------------ |
30+
| `CNAME` | `<YOUR_SHOP_DOMAIN>` | `shops.myshopify.com` | Proxied |
31+
32+
## Product compatibility
33+
34+
<Render
35+
file="provider-guide-compatibility"
36+
product="cloudflare-for-platforms"
37+
/>
38+
39+
## Additional support
40+
41+
<Render file="provider-guide-help" params={{ providerName: "Webflow" }} />
42+
43+
### DNS CAA records
44+
45+
Webflow issues SSL/TLS certificates for merchant domains using Let’s Encrypt and Google Trust Services. If you add any DNS CAA records, you must select **Let’s Encrypt** or **Google Trust Services** as the Certificate Authority (CA) or HTTPS connections may fail.
46+
47+
For more details, refer to [CAA records](/ssl/edge-certificates/caa-records/#caa-records-added-by-cloudflare).

0 commit comments

Comments
 (0)