Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(docs): Update links on gatsby-for-ecommerce #34517

Merged
merged 11 commits into from
Jan 20, 2022
2 changes: 1 addition & 1 deletion docs/docs/conceptual/gatsby-for-ecommerce.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ E-commerce tends to have a number of specific requirements. When building a Gats
- **Persisting a cart across site pages and between sessions** (ie, if the user closes their browser and reopens it tomorrow, the items should still be there). This can be handled either through local-storage or through the shopify-buy JS library.
- **Product search** can be done client-side if the SKU count is small enough to store all products in a global state. Alternatively, it can be handled through the e-commerce provider’s search features, or if those aren’t robust enough, a third-party search provider like Algolia.
- **Surfacing price adjustments** like tax, shipping, discounts/promos to the user while browsing the site. Different e-commerce solutions provide different levels of API access to these objects.
- **Handling checkout.** In order to comply with PCI regulations around storing credit card information, e-commerce providers typically exert strong control over the "buy" or "checkout" experience. Shopify requires all checkout flows using their platform to use their hosted checkout pages, though it's common to wrap them in a subdomain of the main site (e.g. the Gatsby/Shopify site [strivectin.com](strivectin.com) wraps a `myshopify.com` URL under a `shop.strivectin.com` URL for checkout).
- **Handling checkout.** In order to comply with PCI regulations around storing credit card information, e-commerce providers typically exert strong control over the "buy" or "checkout" experience. Shopify requires all checkout flows using their platform to use their hosted checkout pages, though it's common to wrap them in a subdomain of the main site (e.g. the Gatsby/Shopify site [strivectin.com](https://www.strivectin.com/) wraps a `myshopify.com` URL under a `shop.strivectin.com` URL for checkout).
- **Handling account pages.** Again, many sites choose to wrap their e-commerce provider’s account pages under their own domain.

## Additional resources:
Expand Down