Skip to content

Conversation

@jthorne-cf
Copy link
Contributor

  • Update HubSpot's O2O provider guide with Zone Hold details

  • Update SFCC's O2O provider guide with link to SFCC's documentation to migrate a Legacy Zone to Proxy Zone

* Update HubSpot's O2O provider guide with Zone Hold details

* Update SFCC's O2O provider guide with link to SFCC's documentation to migrate a Legacy Zone to Proxy Zone
Copy link
Contributor

@hyperlint-ai hyperlint-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 files reviewed, 1 total issue(s) found.

1. Your SFCC environment must be configured as an "SFCC Proxy Zone". If you currently have an "SFCC Legacy Zone", you cannot enable O2O. More details on the different types of SFCC configurations can be found in the [Salesforce FAQ on SFCC Proxy Zones](https://help.salesforce.com/s/articleView?id=cc.b2c_ecdn_proxy_zone_faq.htm&type=5).
1. Your SFCC environment must be configured as an "SFCC Proxy Zone". If you currently have an "SFCC Legacy Zone", you cannot enable O2O.
* More details on the different types of SFCC configurations can be found in the [Salesforce FAQ on SFCC Proxy Zones](https://help.salesforce.com/s/articleView?id=cc.b2c_ecdn_proxy_zone_faq.htm&type=5).
* Instructions on how to migrate your SFCC environment to an "SFCC Proxy Zone" can be found [here](https://help.salesforce.com/s/articleView?id=cc.b2c_migrate_legacy_zone_to_proxy_zone.htm&type=5).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Instructions on how to migrate your SFCC environment to an "SFCC Proxy Zone" can be found [here](https://help.salesforce.com/s/articleView?id=cc.b2c_migrate_legacy_zone_to_proxy_zone.htm&type=5).
* Instructions on how to migrate your SFCC environment to an "SFCC Proxy Zone" can be found in the [Salesforce migration guide](https://help.salesforce.com/s/articleView?id=cc.b2c_migrate_legacy_zone_to_proxy_zone.htm&type=5).

Issues:

  • Style Guide - (cloudflare.MeaningfulLinkWords-warning) Warning: Rewrite the link text for [here](https://help.salesforce.com/s/articleView?id=cc.b2c_migrate_legacy_zone_to_proxy_zone.htm&type=5) to be more descriptive. For more information, refer to Descriptive link text.

Fix Explanation:

The link text 'here' is not descriptive. Changing it to 'Salesforce migration guide' makes it clear what the link is about, improving accessibility and SEO.

jthorne-cf and others added 5 commits February 5, 2025 11:49
…saas-customers/provider-guides/hubspot.mdx

Co-authored-by: Pedro Sousa <[email protected]>
…saas-customers/provider-guides/hubspot.mdx

Co-authored-by: Pedro Sousa <[email protected]>
…saas-customers/provider-guides/hubspot.mdx

Co-authored-by: Pedro Sousa <[email protected]>
…saas-customers/provider-guides/salesforce-commerce-cloud.mdx

Co-authored-by: Pedro Sousa <[email protected]>
…saas-customers/provider-guides/salesforce-commerce-cloud.mdx

Co-authored-by: Pedro Sousa <[email protected]>
@pedrosousa pedrosousa merged commit 1d16bbe into cloudflare:production Feb 5, 2025
6 checks passed
@workers-devprod workers-devprod added the contribution [Holopin] Recognizes a docs contribution, big or small label Feb 5, 2025
@holopin-bot
Copy link

holopin-bot bot commented Feb 5, 2025

Congratulations @jthorne-cf, the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cm6s9dn1y12200cjo7ej0sl1k

This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account.
Or if you're new to Holopin, you can simply sign up with GitHub, which will do the trick!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

contribution [Holopin] Recognizes a docs contribution, big or small product:cloudflare-for-platforms size/s

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants