@graphcommerce/docs 5.2.0-canary.9 → 6.0.0-canary.20

package/CHANGELOG.md

@@ -1,5 +1,31 @@
 # Change Log
 
+## 6.0.0-canary.20
+
+### Major Changes
+
+- [#1786](https://github.com/graphcommerce-org/graphcommerce/pull/1786) [`26239ef73`](https://github.com/graphcommerce-org/graphcommerce/commit/26239ef73e49731224b227f1eb850dde56d40584) - Bumped minimum version to node16 ([@paales](https://github.com/paales))
+
+## 5.2.0-canary.19
+
+## 5.2.0-canary.18
+
+## 5.2.0-canary.17
+
+## 5.2.0-canary.16
+
+## 5.2.0-canary.15
+
+## 5.2.0-canary.14
+
+## 5.2.0-canary.13
+
+## 5.2.0-canary.12
+
+## 5.2.0-canary.11
+
+## 5.2.0-canary.10
+
 ## 5.2.0-canary.9
 
 ## 5.2.0-canary.8

package/framework/config.md

@@ -0,0 +1,198 @@
+<!-- auto generated -->
+## GraphCommerceConfig
+
+Global GraphCommerce configuration can be configured in your `graphcommerce.config.js` file in the root of your project.
+
+### `canonicalBaseUrl: String!`
+
+The canonical base URL is used for SEO purposes.
+
+Examples:
+- https://example.com
+- https://example.com/en
+- https://example.com/en-US
+
+### `hygraphEndpoint: String!`
+
+The HyGraph endpoint.
+
+Project settings -> API Access -> High Performance Read-only Content API
+
+### `i18n: [GraphCommerceI18nConfig!]!`
+
+All i18n configuration for the project
+
+### `magentoEndpoint: String!`
+
+GraphQL Magento endpoint.
+
+Examples:
+- https://magento2.test/graphql
+
+### `productFiltersPro: Boolean!`
+
+Product filters with better UI for mobile and desktop.
+
+@experimental This is an experimental feature and may change in the future.
+
+### `robotsAllow: Boolean!`
+
+Allow the site to be indexed by search engines.
+If false, the robots.txt file will be set to disallow all.
+
+### `singleProductRoute: Boolean!`
+
+On older versions of GraphCommerce products would use a product type specific route.
+
+This should only be set to false if you use the /product/[url] or /product/configurable/[url] routes.
+
+### `cartDisplayPricesInclTax: Boolean`
+
+Due to a limitation of the GraphQL API it is not possible to determine if a cart should be displayed including or excluding tax.
+
+When Magento's StoreConfig adds this value, this can be replaced.
+
+### `customerRequireEmailConfirmation: Boolean`
+
+Due to a limitation in the GraphQL API of Magento 2, we need to know if the
+customer requires email confirmation.
+
+This value should match Magento 2's configuration value for
+`customer/create_account/confirm` and should be removed once we can query
+
+### `debug: GraphCommerceDebugConfig`
+
+Debug configuration for GraphCommerce
+
+### `demoMode: Boolean`
+
+Enables some demo specific code that is probably not useful for a project:
+
+- Adds the "BY GC" to the product list items.
+- Adds "dominant_color" attribute swatches to the product list items.
+- Creates a big list items in the product list.
+
+### `deployEnvironment: DeployEnvironment`
+
+Environment GraphCommerce is deployed to.
+
+Not to be confused with NODE_ENV: which will always be 'production' when running `next build`.
+
+### `googleAnalyticsId: String`
+
+See https://support.google.com/analytics/answer/9539598?hl=en
+
+Provide a value to enable Google Analytics for your store.
+
+To enable only for a specific locale, override the value in the i18n config.
+
+### `googleRecaptchaKey: String`
+
+Google reCAPTCHA key, get from https://developers.google.com/recaptcha/docs/v3
+
+This value is required even if you are configuring different values for each locale.
+
+### `googleTagmanagerId: String`
+
+The Google Tagmanager ID to be used on the site.
+
+This value is required even if you are configuring different values for each locale.
+
+### `previewSecret: String`
+
+To enable next.js' preview mode, configure the secret you'd like to use.
+
+### `wishlistHideForGuests: Boolean`
+
+Hide the wishlist functionality for guests.
+
+### `wishlistIgnoreProductWishlistStatus: Boolean`
+
+Ignores wether a product is already in the wishlist, makes the toggle an add only.
+
+## GraphCommerceDebugConfig
+
+Debug configuration for GraphCommerce
+
+### `pluginStatus: Boolean`
+
+Reports which plugins are enabled or disabled.
+
+### `webpackCircularDependencyPlugin: Boolean`
+
+Cyclic dependencies can cause memory issues and other strange bugs.
+This plugin will warn you when it detects a cyclic dependency.
+
+When running into memory issues, it can be useful to enable this plugin.
+
+### `webpackDuplicatesPlugin: Boolean`
+
+When updating packages it can happen that the same package is included with different versions in the same project.
+
+Issues that this can cause are:
+- The same package is included multiple times in the bundle, increasing the bundle size.
+- The Typescript types of the package are not compatible with each other, causing Typescript errors.
+
+## GraphCommerceI18nConfig
+
+All i18n configuration for the project
+
+### `locale: String!`
+
+Must be a locale string https://www.unicode.org/reports/tr35/tr35-59/tr35.html#Identifiers
+
+### `magentoStoreCode: String!`
+
+Magento store code.
+
+Stores => All Stores => [Store View] => Store View Code
+
+Examples:
+- default
+- en-us
+- b2b-us
+
+### `canonicalBaseUrl: String`
+
+The canonical base URL is used for SEO purposes.
+
+Examples:
+- https://example.com
+- https://example.com/en
+- https://example.com/en-US
+
+### `cartDisplayPricesInclTax: Boolean`
+
+Due to a limitation of the GraphQL API it is not possible to determine if a cart should be displayed including or excluding tax.
+
+### `defaultLocale: Boolean`
+
+There can only be one entry with defaultLocale set to true.
+- If there are more, the first one is used.
+- If there is none, the first entry is used.
+
+### `domain: String`
+
+Domain configuration, must be a domain https://tools.ietf.org/html/rfc3986
+
+### `googleAnalyticsId: String`
+
+Configure different Google Analytics IDs for different locales.
+
+To disable for a specific locale, set the value to null.
+
+### `googleRecaptchaKey: String`
+
+Locale specific google reCAPTCHA key.
+
+### `googleTagmanagerId: String`
+
+The Google Tagmanager ID to be used per locale.
+
+### `hygraphLocales: [String!]`
+
+Add a gcms-locales header to make sure queries return in a certain language, can be an array to define fallbacks.
+
+### `linguiLocale: String`
+
+Specify a custom locale for to load translations.

package/framework/graphcms.md

@@ -1,28 +1,28 @@
 ---
-menu: GraphCMS
+menu: Hygraph
 ---
 
-# GraphCMS
+# Hygraph
 
-GraphCMS is integrated as a Content Management System. It is used to store all
+Hygraph is integrated as a Content Management System. It is used to store all
 static content and provides a user-friendly interface for managing it.
 
 The [magento-graphcms example](./../getting-started/readme.md) offers a number
 of components to render this content in different ways, for example in the form
 of a page-wide hero banner, a list of USPs or grid of text columns.
 
-This guide covers how to configure GraphCMS and how to build rich content pages
-by adding GraphCMS content to pages.
+This guide covers how to configure Hygraph and how to build rich content pages
+by adding Hygraph content to pages.
 
 ## Configuration
 
-To connect your GraphCommerce app to your GraphCMS project, you'll need a
-GraphCMS project with the required schema.
-[Clone the demo GraphCMS project ↗](https://app.graphcms.com/clone/caddaa93cfa9436a9e76ae9c0F34d257)
+To connect your GraphCommerce app to your Hygraph project, you'll need a Hygraph
+project with the required schema.
+[Clone the demo Hygraph project ↗](https://app.graphcms.com/clone/caddaa93cfa9436a9e76ae9c0F34d257)
 as your starting point. Update the variable in the /.env file:
 
 `GRAPHCMS_URL=""`  
-GraphCMS API URL. Once logged in, copy it from Project Settings > Api Access >
+Hygraph API URL. Once logged in, copy it from Project Settings > Api Access >
 Content API
 
 ## Adding content to pages
@@ -33,15 +33,15 @@ the concept of pages. When a file is added to the /pages directory, it's
 automatically available as a route. Magento category routes are handled by the
 `/pages/[...url].tsx` page.
 
-To add GraphCMS content to, for example, a category page, create a Page entry in
-GraphCMS and match the value of the URL field with the route of the page you
-wish to add content to.
+To add Hygraph content to, for example, a category page, create a Page entry in
+Hygraph and match the value of the URL field with the route of the page you wish
+to add content to.
 
-For example, the content of the 'men' Page entry in GraphCMS:
+For example, the content of the 'men' Page entry in Hygraph:
 
 <figure>
 
-![Page entry in GraphCMS](https://user-images.githubusercontent.com/1251986/157831167-706b54e8-ab25-4e67-882d-dd9595e87d5a.png)
+![Page entry in Hygraph](https://user-images.githubusercontent.com/1251986/157831167-706b54e8-ab25-4e67-882d-dd9595e87d5a.png)
 
 </figure>
 
@@ -64,4 +64,4 @@ Is used to add a`RowProduct (variant:Grid)` and a
 ## Next steps
 
 - Learn how to
-  [build a custom GraphCMS component](../getting-started/graphcms-component.md)
+  [build a custom Hygraph component](../getting-started/graphcms-component.md)

package/framework/plugins-react.md

@@ -171,11 +171,11 @@ work for other things such as:
 
 ### Conditionally include a plugin
 
-Provide an ifEnv export in the plugin that will only include the plugin if the
-environment variable is set.
+Provide an ifConfig export in the plugin that will only include the plugin if a
+configuration value is truety.
 
 ```tsx
-export const ifEnv = 'MY_ENV_VARIABLE'
+export const ifConfig = 'googleAnalytics'
 ```
 
 ### When to use a plugin?

package/framework/readme.md

@@ -16,15 +16,15 @@ high-end e-commerce progressive web apps (PWA).
 | [Static generation](../framework/static-generation.md)         | [Theming](../framework/theming.md)       | [Translations](../framework/translations.md)       |
 | [Environment Variables](../framework/environment-variables.md) | [Typography](../framework/typography.md) | [Troubleshooting](../framework/troubleshooting.md) |
 | [Deployment](../framework/deployment.md)                       | [Favicon](../framework/favicon.md)       | [SEO](../framework/seo.md)                         |
-| [GraphCMS](../framework/graphcms.md)                           | [Icons](../framework//icons.md)          |                                                    |
+| [Hygraph](../framework/graphcms.md)                            | [Icons](../framework//icons.md)          |                                                    |
 
 ## GraphCommerce project structure
 
 When you create a GraphCommerce app, the GraphCommerce
 [magento-graphcms example](../getting-started/readme.md) comes with a basic file
-structure of a GraphCommerce project that's integrated with Magento and
-GraphCMS. Most of the files that you'll work within your GraphCommerce project
-are located in the /components or /pages directories.
+structure of a GraphCommerce project that's integrated with Magento and Hygraph.
+Most of the files that you'll work within your GraphCommerce project are located
+in the /components or /pages directories.
 
 - A minimal set of components you would most likely modify for your project
 - The main layout component, which renders header, navigation, and footer
@@ -40,7 +40,7 @@ File structure of the graphcommerce-magento example
     └── Layout
         └── Footer.tsx
         └── LayoutFull.tsx
-    └── GraphCMS
+    └── Hygraph
         └── Asset
         └── RowHeroBanner
         └── RowQuote

package/getting-started/create.md

@@ -38,18 +38,17 @@ After you've finished this tutorial, you'll have accomplished the following:
 You've familiarized yourself with
 [React ↗](https://reactjs.org/docs/getting-started.html),
 [Next.js ↗](https://nextjs.org/docs/getting-started), and
-[Mui ↗](https://mui.com/getting-started/installation/). GraphCommerce is a
-front-end React framework that uses Next.js for server-side rendering.
+[Mui ↗](https://mui.com/material-ui/getting-started/overview/). GraphCommerce is
+a front-end React framework that uses Next.js for server-side rendering.
 
 ### Install dependencies
 
 If you want to test a GraphCommerce storefront using a pre-configured Magento
-demo store and a pre-configured GraphCMS project with demo content, then you
-need to only install the dependencies. This is the quickest approach.
+demo store and a pre-configured Hygraph project with demo content, then you need
+to only install the dependencies. This is the quickest approach.
 
-- Install and use node 14/16/18: `nvm install 16` or `nvm use 16`
-- Install yarn: `corepack enable` (for node 16/18) or
-  `npm install --global yarn` (for node 14)
+- Install and use node 16/18: `nvm install 16` or `nvm use 16`
+- Install yarn: `corepack enable`
 
 ## Step 1: Create a new GraphCommerce app
 
@@ -75,27 +74,27 @@ https://user-images.githubusercontent.com/1251986/158647122-dc57002f-a9c2-4661-a
 5. `cp -R .env.example .env` — create .env file
 6. `rm CHANGELOG.md` — remove changelog
 
-## Step 2: Magento and GraphCMS API keys
+## Step 2: Magento and Hygraph API keys
 
 > By default, the .env file is configured with API keys from a demo Magento
-> store and a demo GraphCMS project. If you want to test your GraphCommerce app
+> store and a demo Hygraph project. If you want to test your GraphCommerce app
 > using the demo store, then you can start the development environment. Only
 > proceed with the following steps if you want to develop a GraphCommerce
-> storefront using your own Magento store and/or GraphCMS project.
+> storefront using your own Magento store and/or Hygraph project.
 
 ### Requirements
 
 To order to be able to connect your GraphCommerce app to your Magento backend
-and/or GraphCMS project, you'll need:
+and/or Hygraph project, you'll need:
 
 - Magento 2.4.3 - Clean install, a production or a development environment
-- GraphCMS - A GraphCMS project with the required schema.
-  [Clone the demo GraphCMS project ↗](https://app.graphcms.com/clone/caddaa93cfa9436a9e76ae9c0F34d257)
+- Hygraph - A Hygraph project with the required schema.
+  [Clone the demo Hygraph project ↗](https://app.graphcms.com/clone/caddaa93cfa9436a9e76ae9c0F34d257)
   as your starting point.
 
 ### Configuration
 
-To connect your GraphCommerce app to your Magento backend and/or GraphCMS
+To connect your GraphCommerce app to your Magento backend and/or Hygraph
 project, you need to update variables in the /.env file. The .env file contains
 useful information about your storefront.
 
@@ -106,7 +105,7 @@ Magento 2 API URL, located at `http://<magento2-server>/graphql`.
 Comma-separated list of image domains. Add media.graphcms.com as default.
 
 `GRAPHCMS_URL=""`  
-GraphCMS API URL. Once logged in, copy it from Project Settings > Api Access >
+Hygraph API URL. Once logged in, copy it from Project Settings > Api Access >
 Content API
 
 `NEXT_PUBLIC_LOCALE_STORES='{"en-us": "default", "en-ca": "canada"}'`  

package/getting-started/graphcms-component.md

@@ -1,14 +1,14 @@
 ---
-menu: 5. Build a GraphCMS component
-metaTitle: Build a GraphCMS component
+menu: 5. Build a Hygraph component
+metaTitle: Build a Hygraph component
 ---
 
-# Build a GraphCMS component
+# Build a Hygraph component
 
 Previously, you created a GraphCommerce app and started building a custom
-header. You're now ready to build a GraphCMS component.
+header. You're now ready to build a Hygraph component.
 
-GraphCMS is the integrated Content Management System that is part of the
+Hygraph is the integrated Content Management System that is part of the
 [magento-graphcms example](../getting-started/readme.md).
 
 In this tutorial, you'll accomplish a series of tasks to add some specific
@@ -17,7 +17,7 @@ you'll learn where to find resources to build more complex features on your own.
 
 ### After you've finished this tutorial, you'll have accomplished the following:
 
-- Create a Model in GraphCMS, called Banner
+- Create a Model in Hygraph, called Banner
 - Configure the Model's copy and image field
 - Define the relationship between the Banner Model and Page Content field
 - Write a GraphQL query fragment and add it to the page query
@@ -33,9 +33,9 @@ frontend React framework that uses Next.js for server-side rendering.
 
 ---
 
-### Create the GraphCMS model
+### Create the Hygraph model
 
-- Login to GraphCMS, navigate to the Schema and add a new Model called "Banner"
+- Login to Hygraph, navigate to the Schema and add a new Model called "Banner"
 - Add a single line text field called "Identity" and configure the following:
 
 <figure>
@@ -240,9 +240,9 @@ const defaultRenderer: Partial<ContentTypeRenderer> = {
 
 <figure>
 
-![An instance of the banner component rendering with content from GraphCMS](https://user-images.githubusercontent.com/1251986/157832263-ee06b20e-acac-4f68-89f2-4377199b7fa4.png)
+![An instance of the banner component rendering with content from Hygraph](https://user-images.githubusercontent.com/1251986/157832263-ee06b20e-acac-4f68-89f2-4377199b7fa4.png)
 
-   <figcaption>An instance of the banner component rendering with content from GraphCMS</figcaption>
+   <figcaption>An instance of the banner component rendering with content from Hygraph</figcaption>
 </figure>
 
 <figure>

package/getting-started/pages.md

@@ -17,7 +17,7 @@ learn where to find resources to build more complex features on your own.
 
 - Create a new route
 - Add the page GraphQL queries required to render the layout (header, footer)
-- Use getStaticProps to fetch GraphCMS data
+- Use getStaticProps to fetch Hygraph data
 - Use getStaticPaths to provide a list of all URLs to pre-render
 
 ### Requirements
@@ -126,16 +126,16 @@ fetch information about the Magento storeview. Then, the query
 footer and page content.
 
 In this example, the URL variable is empty. As a result, the
-`...PageContentQueryFragment` will have no result when trying to fetch a
-GraphCMS page with URL `''`.
+`...PageContentQueryFragment` will have no result when trying to fetch a Hygraph
+page with URL `''`.
 
 The function `getStaticProps` is used to fetch data, meaning content is rendered
 on the server. Review the page's source code and search for `About Us` to
 validate that this string (currently hard-coded) is part of the source code.
 
-### Add GraphCMS content to the page
+### Add Hygraph content to the page
 
-- Login to GraphCMS, navigate to Content and add a new Page entry with URL:
+- Login to Hygraph, navigate to Content and add a new Page entry with URL:
   about/about-us
 - In /about/about-us.tsx, make the following change to `getStaticProps`:
 
@@ -161,16 +161,16 @@ function AboutUs({ pages }: Props) {
 
 <figure>
 
-![Fetch page content from GraphCMS](https://user-images.githubusercontent.com/1251986/157832923-a2b47e92-ae7c-4557-bc54-a0b04e0d6d7e.png)
+![Fetch page content from Hygraph](https://user-images.githubusercontent.com/1251986/157832923-a2b47e92-ae7c-4557-bc54-a0b04e0d6d7e.png)
 
-  <figcaption>Fetch page content from GraphCMS</figcaption>
+  <figcaption>Fetch page content from Hygraph</figcaption>
 </figure>
 
 <figure>
 
-![GraphCMS entry](https://user-images.githubusercontent.com/1251986/157832975-dc56d48c-a1ef-41d9-9f7c-67d2f19250e4.png)
+![Hygraph entry](https://user-images.githubusercontent.com/1251986/157832975-dc56d48c-a1ef-41d9-9f7c-67d2f19250e4.png)
 
-  <figcaption>GraphCMS entry</figcaption>
+  <figcaption>Hygraph entry</figcaption>
 </figure>
 
 ### Add pre-rendering with getStaticPaths
@@ -225,7 +225,7 @@ built-time will not result in a 404:
 > for the HTML to be generated, identical to SSR (hence why blocking), and then
 > be cached for future requests so it only happens once per path.
 
-### Pre-render all /about/ pages from GraphCMS
+### Pre-render all /about/ pages from Hygraph
 
 - In /about/[url].tsx, replace the getStaticPaths function with the following:
 
@@ -254,7 +254,7 @@ export const getStaticPaths: GetPageStaticPaths = async (context) => {
 }
 ```
 
-The PagesStaticPathsDocument query is used to fetch all pages from GraphCMS that
+The PagesStaticPathsDocument query is used to fetch all pages from Hygraph that
 have a URL starting with 'about'. The locale options from the context object are
 used to create an array:
 
@@ -288,4 +288,4 @@ You can test the static build process by running it locally:
 ## Next steps
 
 - Learn how to
-  [build a custom GraphCMS component](../getting-started/graphcms-component.md)
+  [build a custom Hygraph component](../getting-started/graphcms-component.md)

package/getting-started/readme.md

@@ -100,6 +100,8 @@ also applies if you want to modify a component's or
 
 | Packages (/node_modules directory/)          |                                                            |
 | -------------------------------------------- | ---------------------------------------------------------- |
+| @graphcommerce/address-fields-nl             | [Source](../../../packages/address-fields-nl/)             |
+| @graphcommerce/cli                           | [Source](../../../packages/cli/)                           |
 | @graphcommerce/framer-next-pages             | [Source](../../../packages/framer-next-pages/)             |
 | @graphcommerce/googleanalytics               | [Source](../../../packages/googleanalytics/)               |
 | @graphcommerce/googlerecaptcha               | [Source](../../../packages/googlerecaptcha/)               |
@@ -144,9 +146,9 @@ also applies if you want to modify a component's or
 | @graphcommerce/react-hook-form               |                                                            |
 | @graphcommerce/typescript-config-pwa         |                                                            |
 
-## GraphCMS
+## Hygraph
 
-GraphCMS is integrated as a Content Management System. It is used to store all
+Hygraph is integrated as a Content Management System. It is used to store all
 static content and provides a user-friendly interface for managing it.
 
 The magento-graphcms example offers a number of components to render this
@@ -154,7 +156,7 @@ content in different ways, for example in the form of a page-wide hero banner, a
 list of USPs or grid of text columns.
 
 To [get started](../getting-started/create.md) with the magento-graphcms
-example, cloning the demo GraphCMS project GraphQL schema and its content is
+example, cloning the demo Hygraph project GraphQL schema and its content is
 recommended.
 
 ## Pages
@@ -200,10 +202,10 @@ Page structure of the graphcommerce-magento example
 GraphCommerce is built and optimized to use data coming from Magento's GraphQL
 API. GraphCommerce uses GraphQL Mesh, which adds the ability to add extra
 (micro)services as data sources. In the magento-graphcms example, a headless CMS
-called [GraphCMS](../getting-started/../framework/graphcms.md) is integrated.
+called [Hygraph](../getting-started/../framework/graphcms.md) is integrated.
 
 By default, the GraphQL Mesh endpoint runs on route /api/graphql. You can query
-both the Magento GraphQL schema and the GraphCMS GraphQL schema. Try out the
+both the Magento GraphQL schema and the Hygraph GraphQL schema. Try out the
 GraphCommerce demo
 [GraphQL Explorer ↗](https://graphcommerce.vercel.app/api/graphql) with the
 following example query:
@@ -244,12 +246,12 @@ GraphQL queries in the graphcommerce-magento example
 
 ├── GraphQL
     └── CategoryPage.graphql
+    └── DefaultPage.graphql
     └── PageLink.graphql
     └── DefaultPage.graphql
     └── PagesStaticPaths.graphql
-    └── FooterQueryFragment.graphql
-    └── PageContentQueryFragment.graphql
     └── ProductPage.graphql
+    └── ProductPage2.graphql
 ```
 
 ## FAQ

package/package.json

@@ -2,10 +2,10 @@
   "name": "@graphcommerce/docs",
   "homepage": "https://www.graphcommerce.org/docs",
   "repository": "github:graphcommerce-org/graphcommerce/docs",
-  "version": "5.2.0-canary.9",
+  "version": "6.0.0-canary.20",
   "sideEffects": true,
   "devDependencies": {
-    "@graphcommerce/prettier-config-pwa": "5.2.0-canary.9"
+    "@graphcommerce/prettier-config-pwa": "6.0.0-canary.20"
   },
   "prettier": "@graphcommerce/prettier-config-pwa"
 }

package/readme.md

@@ -44,7 +44,7 @@ https://user-images.githubusercontent.com/1251986/154977573-4015e77c-43e7-481e-a
 GraphCommerce offers a [magento-graphcms](./getting-started/readme.md) example
 that provides a full-featured storefront. The example integrates with your
 Magento backend and provides a full purchase journey out-of-the-box. It uses
-GraphCMS to enrich pages with multiple content components, like the homepage.
+Hygraph to enrich pages with multiple content components, like the homepage.
 
 The magento-graphcms example is styled using the Mui component library. You can
 start styling by making changes to the [theme](./framework/theming.md).

package/roadmap.md

@@ -29,7 +29,7 @@ The following overview contains the status of items on the GraphCommerce roadmap
 - [x] Configurable product image swatches
       [example ↗](https://graphcommerce.vercel.app/nl/p/gc-puncturing-sock)
 - [x] Virtual product, downloadable products
-- [x] Multilingual Hygraph (GraphCMS) setup support
+- [x] Multilingual Hygraph (Hygraph) setup support
 - [x] Multisafepay payment service
 - [x] Multilingual product sitemap generation
 - [x] Multi level Navigation (Mega Menu)
@@ -49,7 +49,7 @@ The following overview contains the status of items on the GraphCommerce roadmap
 
 ## Future
 
-- [ ] `magento` example without GraphCMS
+- [ ] `magento` example without Hygraph
 - [ ] PageBuilder support
 
 ## Next steps