@graphcommerce/docs 7.0.0-canary.21 → 7.0.1-canary.0

package/CHANGELOG.md

@@ -1,6 +1,212 @@
 # Change Log
 
-## 7.0.0-canary.21
+## 7.0.1-canary.0
+
+### Patch Changes
+
+- [#2047](https://github.com/graphcommerce-org/graphcommerce/pull/2047) [`136580b39`](https://github.com/graphcommerce-org/graphcommerce/commit/136580b39e3cffdd07e3fa087e049bd532c3e8f1) - Updated all dependencies to the latest version where possible. ([@paales](https://github.com/paales))
+
+## 7.0.0
+
+### Patch Changes
+
+- [#1933](https://github.com/graphcommerce-org/graphcommerce/pull/1933) [`e644887a7`](https://github.com/graphcommerce-org/graphcommerce/commit/e644887a75a3801a8b0dcf39558f56110a51d774) - Updated ReCAPTCHA docs ([@bramvanderholst](https://github.com/bramvanderholst))
+
+- [`2f479c830`](https://github.com/graphcommerce-org/graphcommerce/commit/2f479c830e84137b739d83bc6dd1e36a6e299e3a) - Added advise about URL suffixes ([@paales](https://github.com/paales))
+
+- [#2034](https://github.com/graphcommerce-org/graphcommerce/pull/2034) [`6fca47484`](https://github.com/graphcommerce-org/graphcommerce/commit/6fca474847fe52f004a6ac0abbd88492512b46ad) - Pre-resolve the customFetch in mesh config, so that it works with the new mesh version. ([@paales](https://github.com/paales))
+
+- [#1978](https://github.com/graphcommerce-org/graphcommerce/pull/1978) [`0c91ac1f7`](https://github.com/graphcommerce-org/graphcommerce/commit/0c91ac1f70f58dec418e945fc4a6a8c6732cc21e) - When a user selects a variant, it will switch the values on the configurable page with the values of the configured variant. Enabling options here will allow switching of those variants. ([@carlocarels90](https://github.com/carlocarels90))
+
+- [#1957](https://github.com/graphcommerce-org/graphcommerce/pull/1957) [`cb3c82163`](https://github.com/graphcommerce-org/graphcommerce/commit/cb3c82163c32768f977b85c21b029ead354847af) - Docs were directly applied to the config.md which is autogenerated ([@paales](https://github.com/paales))
+
+- [#2020](https://github.com/graphcommerce-org/graphcommerce/pull/2020) [`c9ab0e827`](https://github.com/graphcommerce-org/graphcommerce/commit/c9ab0e827cbf866000a2184ee7fa38b123aa2cd2) - Update docs for Enable Guest Checkout Login setting ([@SimonPrins](https://github.com/SimonPrins))
+
+- [#1959](https://github.com/graphcommerce-org/graphcommerce/pull/1959) [`d0809b132`](https://github.com/graphcommerce-org/graphcommerce/commit/d0809b132a0e4cbdfeb86164f6c16a89ebecd987) - Added support for default values in the Config.graphqls files for the documentation ([@JoshuaS98](https://github.com/JoshuaS98))
+
+## 6.2.0-canary.98
+
+## 6.2.0-canary.97
+
+## 6.2.0-canary.96
+
+## 6.2.0-canary.95
+
+## 6.2.0-canary.94
+
+### Patch Changes
+
+- [#2020](https://github.com/graphcommerce-org/graphcommerce/pull/2020) [`c9ab0e827`](https://github.com/graphcommerce-org/graphcommerce/commit/c9ab0e827cbf866000a2184ee7fa38b123aa2cd2) - Update docs for Enable Guest Checkout Login setting ([@SimonPrins](https://github.com/SimonPrins))
+
+## 6.2.0-canary.93
+
+## 6.2.0-canary.92
+
+## 6.2.0-canary.91
+
+## 6.2.0-canary.90
+
+### Patch Changes
+
+- [#2034](https://github.com/graphcommerce-org/graphcommerce/pull/2034) [`6fca47484`](https://github.com/graphcommerce-org/graphcommerce/commit/6fca474847fe52f004a6ac0abbd88492512b46ad) - Pre-resolve the customFetch in mesh config ([@paales](https://github.com/paales))
+
+## 6.2.0-canary.89
+
+## 6.2.0-canary.88
+
+## 6.2.0-canary.87
+
+### Patch Changes
+
+- [#2022](https://github.com/graphcommerce-org/graphcommerce/pull/2022) [`0495db84d`](https://github.com/graphcommerce-org/graphcommerce/commit/0495db84d1d450750bd74b94a379b4e7764a5753) - add documentation for the GraphCommerceStorefrontConfig gallery option. ([@carlocarels90](https://github.com/carlocarels90))
+
+## 6.2.0-canary.86
+
+## 6.2.0-canary.85
+
+## 6.2.0-canary.84
+
+## 6.2.0-canary.83
+
+## 6.2.0-canary.82
+
+## 6.2.0-canary.81
+
+## 6.2.0-canary.80
+
+## 6.2.0-canary.79
+
+## 6.2.0-canary.78
+
+## 6.2.0-canary.77
+
+## 6.2.0-canary.76
+
+## 6.2.0-canary.75
+
+## 6.2.0-canary.74
+
+## 6.2.0-canary.73
+
+### Patch Changes
+
+- [#1978](https://github.com/graphcommerce-org/graphcommerce/pull/1978) [`0c91ac1f7`](https://github.com/graphcommerce-org/graphcommerce/commit/0c91ac1f70f58dec418e945fc4a6a8c6732cc21e) - When a user selects a variant, it will switch the values on the configurable page with the values of the configured variant. Enabling options here will allow switching of those variants. ([@carlocarels90](https://github.com/carlocarels90))
+
+## 6.2.0-canary.72
+
+## 6.2.0-canary.71
+
+## 6.2.0-canary.70
+
+## 6.2.0-canary.69
+
+## 6.2.0-canary.68
+
+## 6.2.0-canary.67
+
+## 6.2.0-canary.66
+
+## 6.2.0-canary.65
+
+## 6.2.0-canary.64
+
+## 6.2.0-canary.63
+
+## 6.2.0-canary.62
+
+## 6.2.0-canary.61
+
+## 6.2.0-canary.60
+
+## 6.2.0-canary.59
+
+## 6.2.0-canary.58
+
+## 6.2.0-canary.57
+
+## 6.2.0-canary.56
+
+## 6.2.0-canary.55
+
+## 6.2.0-canary.54
+
+## 6.2.0-canary.53
+
+## 6.2.0-canary.52
+
+## 6.2.0-canary.51
+
+### Patch Changes
+
+- [`2f479c830`](https://github.com/graphcommerce-org/graphcommerce/commit/2f479c830e84137b739d83bc6dd1e36a6e299e3a) - Added advise about URL suffixes ([@paales](https://github.com/paales))
+
+## 6.2.0-canary.50
+
+## 6.2.0-canary.49
+
+### Patch Changes
+
+- [#1959](https://github.com/graphcommerce-org/graphcommerce/pull/1959) [`d0809b132`](https://github.com/graphcommerce-org/graphcommerce/commit/d0809b132a0e4cbdfeb86164f6c16a89ebecd987) - Added support for default values in the Config.graphqls files for the documentation ([@JoshuaS98](https://github.com/JoshuaS98))
+
+## 6.2.0-canary.48
+
+## 6.2.0-canary.47
+
+## 6.2.0-canary.46
+
+## 6.2.0-canary.45
+
+## 6.2.0-canary.44
+
+## 6.2.0-canary.43
+
+## 6.2.0-canary.42
+
+## 6.2.0-canary.41
+
+## 6.2.0-canary.40
+
+## 6.2.0-canary.39
+
+### Patch Changes
+
+- [#1957](https://github.com/graphcommerce-org/graphcommerce/pull/1957) [`cb3c82163`](https://github.com/graphcommerce-org/graphcommerce/commit/cb3c82163c32768f977b85c21b029ead354847af) - Docs were directly applied to the config.md which is autogenerated ([@paales](https://github.com/paales))
+
+## 6.2.0-canary.38
+
+## 6.2.0-canary.37
+
+## 6.2.0-canary.36
+
+## 6.2.0-canary.35
+
+## 6.2.0-canary.34
+
+## 6.2.0-canary.33
+
+## 6.2.0-canary.32
+
+## 6.2.0-canary.31
+
+## 6.2.0-canary.30
+
+## 6.2.0-canary.29
+
+## 6.2.0-canary.28
+
+## 6.2.0-canary.27
+
+## 6.2.0-canary.26
+
+## 6.2.0-canary.25
+
+## 6.2.0-canary.24
+
+## 6.2.0-canary.23
+
+## 6.2.0-canary.22
+
+## 6.2.0-canary.21
 
 ## 6.2.0-canary.20
 

package/feature-list.md

@@ -158,7 +158,8 @@ Features taken from the Magento Commerce 2 Feature List
 - [ ] Control which products and categories can be viewed by each customer
       group. — [Commerce]
 - [ ] Show side-by-side product comparisons with two or more products. — [Todo]
-- [ ] Display recently viewed and compared products. — [Todo]
+- [ ] Display recently viewed products. — [Todo]
+- [x] Compare products. — [Enhanced]
 - [x] Increase search relevancy and scalability with Elasticsearch technology.
 - [x] Set stop words, attribute weightings, and search synonyms for higher
       conversions.

package/framework/config.md

@@ -115,11 +115,30 @@ When Magento's StoreConfig adds this value, this can be replaced.
 
 Use compare functionality
 
-#### `compareVariant: [CompareVariant](#CompareVariant)`
+#### `compareVariant: [CompareVariant](#CompareVariant) (default: ICON)`
 
 By default the compare feature is denoted with a 'compare ICON' (2 arrows facing one another).
 This may be fine for experienced users, but for more clarity it's also possible to present the compare feature as a CHECKBOX accompanied by the 'Compare' label
 
+#### `configurableVariantForSimple: Boolean (default: [object Object])`
+
+If a simple product is part of a Configurable product page, should the simple product be
+rendered as a configured option of the configurable product page?
+
+How does this work:
+
+When the `products(filters: { url_key: { eq: 'simple-product' } }) { ... }` query is ran,
+Magento also returns the Simple product and the Configurable product the simple belongs to.
+
+If that is the case we render the configurable product page instead of the simple product page but
+the options to select the simple product are pre-selected.
+
+#### `configurableVariantValues: [MagentoConfigurableVariantValues](#MagentoConfigurableVariantValues) (default: [object Object])`
+
+When a user selects a variant, it will switch the values on the configurable page with the values of the configured variant.
+
+Enabling options here will allow switching of those variants.
+
 #### `customerRequireEmailConfirmation: Boolean`
 
 Due to a limitation in the GraphQL API of Magento 2, we need to know if the
@@ -132,7 +151,7 @@ This value should match Magento 2's configuration value for
 
 Debug configuration for GraphCommerce
 
-#### `demoMode: Boolean`
+#### `demoMode: Boolean (default: true)`
 
 Enables some demo specific code that is probably not useful for a project:
 
@@ -150,21 +169,24 @@ To override the value for a specific locale, configure in i18n config.
 
 #### `googleRecaptchaKey: String`
 
-Google reCAPTCHA site key.  
-When using reCAPTCHA, this value is required, even if you are configuring different values for each locale.  
+Google reCAPTCHA site key.
+When using reCAPTCHA, this value is required, even if you are configuring different values for each locale.
 
 Get a site key and a secret key from https://developers.google.com/recaptcha/docs/v3
 
 The secret key should be added in the Magento admin panel (Stores > Configuration > Security > Google ReCAPTCHA Storefront > reCAPTCHA v3 Invisible)
 ReCAPTCHA can then be enabled/disabled for the different forms, separately (Stores > Configuration > Security > Google ReCAPTCHA Storefront > Storefront)
 
-
 #### `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.
 
+#### `hygraphProjectId: String`
+
+Hygraph Project ID. **Only used for migrations.**
+
 #### `hygraphWriteAccessEndpoint: String`
 
 Content API. **Only used for migrations.**
@@ -192,6 +214,12 @@ Project settings -> API Access -> Permanent Auth Tokens
   - Delete existing components
   - Update remote sources
   - Delete remote sources
+  - Read existing environments
+  - Read public content views
+  - Create public content views
+  - Update public content views
+  - Delete public content views
+  - Can see schema view
 
 ```
 GC_HYGRAPH_WRITE_ACCESS_ENDPOINT="https://...hygraph.com/v2/..."
@@ -215,12 +243,16 @@ Limit the static generation of SSG when building
 
 To enable next.js' preview mode, configure the secret you'd like to use.
 
+#### `productFiltersLayout: [ProductFiltersLayout](#ProductFiltersLayout) (default: DEFAULT)`
+
+Layout how the filters are rendered.
+DEFAULT: Will be rendered as horzontal chips on desktop and mobile
+SIDEBAR: Will be rendered as a sidebar on desktop and horizontal chips on mobile
+
 #### `productFiltersPro: Boolean`
 
 Product filters with better UI for mobile and desktop.
 
-@experimental This is an experimental feature and may change in the future.
-
 #### `productRoute: String`
 
 By default we route products to /p/[url] but you can change this to /product/[url] if you wish.
@@ -330,4 +362,23 @@ Add a gcms-locales header to make sure queries return in a certain language, can
 
 #### `linguiLocale: String`
 
-Specify a custom locale for to load translations.
+Specify a custom locale for to load translations.
+
+### MagentoConfigurableVariantValues
+
+Options to configure which values will be replaced when a variant is selected on the product page.
+
+#### `content: Boolean`
+
+Use the name, description, short description and meta data from the configured variant
+
+#### `gallery: Boolean`
+
+This option enables the automatic update of product gallery images on the product page when a variant is selected,
+provided that the gallery images for the selected variant differ from the currently displayed images.
+
+#### `url: Boolean`
+
+When a variant is selected the URL of the product will be changed in the address bar.
+
+This only happens when the actual variant is can be accessed by the URL.

package/framework/favicon.md

@@ -35,6 +35,20 @@ to simplify the process of making correct favicons.
  <figcaption>Favicon sketch template</figcaption>
 </figure>
 
+## Open Graph preview image
+
+The Open Graph image is automaticly set for product and category pages if
+possible. For product pages the first gallary image will be used and for
+category pages the image uploaded to the `Category Image` attribute. If these
+images are not availale or on any of the other other pages a preview image will
+not be added unless added as `ogImage` prop to the `PageMeta`, `, CategoryMeta`
+or `ProductPageMeta` components.
+
+It is possible to enable a fallback image per route by setting the
+`ogImageUseFallback` prop to `true` on either the `PageMeta`, `, CategoryMeta`
+or `ProductPageMeta` components. The image used as fallback can be found at
+`/public/open-graph-image.jpg`
+
 ## Next steps
 
 - Lear more about [Static file serving](../framework/static-file-serving.md)

package/hygraph/cli.md

@@ -0,0 +1,63 @@
+---
+menu: Hygraph cli
+---
+
+# Hygraph migrate cli
+
+It is possible to upgrade your Hygraph schema using the Graphcommerce Hygraph
+CLI: `yarn graphcommerce hygraph-migrate`
+
+This is a tool that automatically modifies your Hygraph schema without having to
+add models, components field and enumerations manually.
+
+Please note that:
+
+- All migrations are backwards compatible with previous versions of
+  GraphCommerce. This means that after running a migration, older versions of
+  GraphCommerce will still work (unless specified otherwise)
+
+- There is no rollback functionality in the Hygraph migrate cli. Please create a
+  copy of the project to test te migration on first. Once you run a migration,
+  you can't undo these schema changes with the CLI. You will be required
+  rollback the from the UI yourself.
+
+### Steps
+
+The following steps are needed to utilize this tool:
+
+1. Create a Hygraph migration token
+   1. Open your Hygraph project. Go to: Project settings > Permanent auth tokens
+   2. Click 'Add token' and give it a name, something like 'GraphCommerce Write
+      Access Token' and keep stage on 'Published'.
+   3. Under 'Management API', click 'Yes, Initialize defaults'
+   4. Click 'Edit Permissions' and enable: 'Update' and 'Delete' permissions for
+      'models', 'enumerations', 'fields', 'components' and 'sources':
+      - Update existing models
+      - Delete existing models
+      - Update existing fields
+      - Delete existing fields
+      - Update existing enumerations
+      - Delete existing enumerations
+      - Update existing components
+      - Delete existing components
+      - Update remote sources
+      - Delete remote sources
+      - Read existing environments
+      - Read public content views
+      - Create public content views
+      - Update public content views
+      - Delete public content views
+      - Can see schema view
+   5. Add this new token to your env file: `GC_HYGRAPH_WRITE_ACCESS_TOKEN=""`
+2. Add the Content API key to your env file like this:
+   1. Open your Hygraph project. Go to: Project settings -> API Access
+   2. Copy the Content API URL and add to your env file:
+      `GC_HYGRAPH_WRITE_ACCESS_ENDPOINT=""`
+3. Add your hygraphProjectId to your env file like this:
+   1. Copy the project ID from the URL when logged in
+      `https://app.hygraph.com/PROJECT_ID_IS_HERE/master`
+   2. Add the project ID to your env file: `GC_HYGRAPH_PROJECT_ID=””`
+4. Run `yarn graphcommerce hygraph-migrate`
+5. Select the migration you want to run and press enter.
+6. The migrations should now be applied, check your Hygraph Schema if changes
+   are made.

package/hygraph/dynamic-rows.md

@@ -0,0 +1,107 @@
+# Hygraph Dynamic Rows
+
+Dynamic Rows offer the ability to add rows to multiple pages using rule based
+relations (instead of adding a row to each page manually). These rules are based
+on common properties between those pages. An example of such property would be
+the category. Let's take a deeper look.
+
+> Note
+>
+> The Dynamic Row functionality is available since Graphcommerce 7.0.0
+
+## Example of injecting a Dynamic Row
+
+Let's say we want to inject a Dynamic Row which displays a discount banner for
+all socks with animal prints with a price lower than €7.50. We want to place it
+after the product specs:
+
+1. We name the Dynamic Row `discount-banner-row`
+2. The row we want to inject. In this case the row `discount-banner`.
+   ![row-to-insert](https://github.com/graphcommerce-org/graphcommerce/assets/1244416/5cada894-daef-45ef-bbb9-0ddedca0ecf5)
+3. We set the placement on `AFTER`
+4. The placement target will be `product-specs`
+5. For the conditions we will use the `Text` and `Number` components nested in
+   an `AND` component.
+
+The result is as follows:
+
+![dynamic-row-fields](https://github.com/graphcommerce-org/graphcommerce/assets/1244416/d3f26e9e-0ad0-4713-86a8-67f2fa2b6a97)
+
+The Dynamic Row should now be injected on all the pages whose properties match
+the conditions.
+
+## How does it work?
+
+The magic of the Dynamic Row functionality, is all in the `HygrahPageContent()`
+function. This function takes 4 arguments.
+
+1. The graphql client
+2. The current page URL
+3. Optional: The properties to match the dynamic row with. This should be an
+   object.
+4. Optional: Cached (standard false)
+
+## The structure of a Dynamic Row
+
+To inject a dynamic row, go to Hygraph and add a Dynamic Row entry. You will see
+the following fields:
+
+1. Internal name. This is the name of the Dynamic Row.
+2. Row. This is the Row you want to inject. i.e. a Row Column One or a Row
+   Links.
+3. Placement. You can place the injection before or after the placement target.
+   You can also replace the placement target.
+4. Placement Target. The row you want to place the Dynamic row before, after or
+   replaced.
+5. Conditions. Here you will match which pages should display the dynamic row.
+
+### Placement
+
+Placement has a few key behaviours.
+
+1. When placement target is empty or not found, and before is selected, the
+   Dynamic Row will be placed before all other rows.
+2. When placement target is empty or not found, and after or replace is
+   selected, the Dynamic Row will be placed after all other rows.
+3. When placement target is found, the injected row will be placed before, after
+   or replace the placement target accordingly.
+
+### Conditions
+
+The conditions are matched against the properties of the pages you want to
+inject into. As explained in 'How does it work?' we can give an object of
+properties to a page. You can add a custom object to the `HygraphPageContent()`
+in your own NextJS pages. You can then use the conditions field in Hygraph to
+match those properties.
+
+The conditions field works as follows:
+
+- We can match against string or number values using the Text and Number
+  components.
+- Text and Number components contain a property and a value field. This way we
+  can match values against the page properties. If there is a match the Dynamic
+  Row will be injected.
+- The property can be accessed with javascript dot notation. If the object
+  contains an array of objects, you don't have to use bracket notation. Let's
+  say categories is an array of category objects which hold the category name:
+
+  ```tsx
+    {
+      categories [
+        {
+          name: "Animals",
+        },
+        {
+          name: "Landscapes",
+        },
+      ]
+    }
+  ```
+
+  In this case, the property field can be accessed using `categories.name`
+  syntax.
+
+- Number components contain an additional field called operator. Here we can
+  match if a number is equal to, greater than or lower than.
+- We can implement logic with the And & Or components. These components allow
+  nesting of Text and Number components.

package/{framework/graphcms.md → hygraph/readme.md}

@@ -1,5 +1,5 @@
 ---
-menu: Hygraph
+menu: Overview
 ---
 
 # Hygraph
@@ -66,3 +66,4 @@ Is used to add a`RowProduct (variant:Grid)` and a
 
 - Learn how to
   [build a custom Hygraph component](../getting-started/graphcms-component.md)
+  - Learn how to [upgrade your Hygraph schema](./upgrading.md)

package/magento/configurable-products.md

@@ -0,0 +1,86 @@
+---
+menu: Configurable Products
+---
+
+# Configurable Products
+
+Example:
+[Simple product (with pre-selection)](https://graphcommerce.vercel.app/p/matriarch-s-edges-size-4-6y-gc-469-sock-6y)
+
+GraphCommerce enables various ways to manage the display of data from
+configurable products in Magento. This flexibility allows you to choose dynamic
+updates for the following data:
+
+- **Content:** Name, description, short description, and meta-data from the
+  selected variant.
+- **Gallery:** Automatically updates product gallery images on the product page
+  when a variant is chosen, provided the gallery images for the selected variant
+  differ from the currently displayed ones.
+- **URL:** The product URL changes in the address bar when a variant is
+  selected, but this only happens when the actual variant can be accessed via
+  the URL.
+
+## Displaying the configured variant on a configurable product page for a simple product
+
+Add the following to your `graphcommerce.config.js` file:
+
+Determines whether a simple product should appear as a Configurable Product with
+pre-selected options or as the default Simple Product.
+
+### How does this work?
+
+When the `products(filters: { url_key: { eq: 'simple-product' } }) { ... }`
+query is ran, Magento also returns besides the requested Simple product also the
+Configurable product the simple belongs to.
+
+If that is the case we render the Configurable Product page instead of the
+Simple Product page, but the options for the Simple Product are pre-selected.
+
+```js
+const config = {
+  configurableVariantForSimple: true,
+}
+module.exports = config
+```
+
+## Switching content when a variant is selected
+
+Add the following to your `graphcommerce.config.js` file:
+
+- `url`: When a variant is selected the URL of the product will be changed in
+  the address bar. Note that this only occurs when the actual variant can be
+  accessed through the URL.
+
+- `content`: Use the name, description, short description and meta data from the
+  configured variant
+
+- `gallery`: This option enables the automatic update of product gallery images
+  on the product page when a variant is selected, provided that the gallery
+  images for the selected variant differ from the currently displayed images.
+
+```js
+const config = {
+  configurableVariantValues: {
+    url: true,
+    gallery: true,
+    content: true,
+  },
+}
+```
+
+## Magento configuration
+
+### How to configure the simple and configurable products to use this feature?
+
+By default Magento will return the simple and configurable for a simple variant,
+no configuration required.
+
+To make the automatic swithcing of URL's possible, make sure the simple product
+has a URL by making sure it's visibility is set something different than
+`Not Visible Individually`: `Catalog`, `Catalog, Search` or `Search`.
+
+`Catalog -> Products -> [product] -> Visibility: [Catalog / Catalog, Search / Search]`
+
+## Next steps
+
+- [Overview](./readme)

package/magento/readme.md

@@ -50,6 +50,30 @@ For Magento Open Source:
 For Adobe Commerce:
 `Stores -> Attributes -> Customer Address -> street -> Lines Count`
 
+### Remove URL suffixes from products and categorories (optional)
+
+GraphCommerce does not support URL suffixes, because Next.js can not handle urls
+ending in `.html`. When migrating from an existing shop, GraphCommerce will
+automatically redirect to the suffix-less URL. However, GraphCommerce will need
+to do an additional query to Magento to find the route.
+
+If you are starting out from a new project, we recommend to remove the URL
+suffixes from products and categories.
+
+Remove the URL suffixes from products and categories. (default is `.html`)
+`Stores -> Configuration -> Catalog -> Catalog -> Search Engine Optimization -> Product URL Suffix`
+`Stores -> Configuration -> Catalog -> Catalog -> Search Engine Optimization -> Category URL Suffix`
+
+### Enable guest checkout login
+
+During customer login, GraphCommerce queries Magento to determine whether the
+customer account already exists. To do this the following setting must be set to
+Yes:
+`Stores -> Configuration -> Sales -> Checkout -> Checkout Options -> Enable Guest Checkout Login`
+
+If this is not set correctly, customers will not be able to log in, since they
+will always be prompted to create a new account.
+
 ## Optional packages
 
 - [Store Pickup / MSI](https://github.com/graphcommerce-org/graphcommerce/tree/main/packages/magento-cart-pickup)

package/package.json

@@ -2,10 +2,10 @@
   "name": "@graphcommerce/docs",
   "homepage": "https://www.graphcommerce.org/docs",
   "repository": "github:graphcommerce-org/graphcommerce/docs",
-  "version": "7.0.0-canary.21",
+  "version": "7.0.1-canary.0",
   "sideEffects": true,
   "devDependencies": {
-    "@graphcommerce/prettier-config-pwa": "7.0.0-canary.21"
+    "@graphcommerce/prettier-config-pwa": "7.0.1-canary.0"
   },
   "prettier": "@graphcommerce/prettier-config-pwa"
 }

package/roadmap.md

@@ -13,18 +13,29 @@ menu: Roadmap
 The following overview contains the status of items on the GraphCommerce roadmap
 (items are subject to change):
 
-## In progress
+## In progress / planned
 
-- [ ] Algolia implementation
-- [ ] Dynamic Row based content
-- [ ] Product compare functionality
-- [ ] Edge runtime for GraphQL Mesh and Streaming SSR rendering
 - [ ] Global store messages
+- [ ] Wishlist redesign
+- [ ] Success page redesign
+- [ ] Product thumbnails on product page
+- [ ] Dutch Postcode API upgrades
+- [ ] Invalid session handling improvements
+- [ ] Performance improvements
+- [ ] Migration to next/image in favor of @graphcommerce/image
 
-## Just released
+## Released
 
 [See all releases](https://github.com/graphcommerce-org/graphcommerce/releases?q=prerelease%3Afalse+&expanded=true)
 
+- [x] Configurable variants for simple products
+      [ocs ↗](https://graphcommerce.org/docs/magento/configurable-products)
+- [x] Cart redesign
+- [x] Hygraph schema migrations
+      [docs ↗](https://graphcommerce.org/docs/hygraph/cli)
+- [x] [Algolia Search (beta)](https://github.com/graphcommerce-org/graphcommerce/tree/main/packages/algolia-search)
+- [x] [Dynamic Rows](https://github.com/graphcommerce-org/graphcommerce/tree/main/packages/hygraph-dynamic-rows)
+- [x] [Product compare](https://github.com/graphcommerce-org/graphcommerce/blob/main/packages/magento-compare/Config.graphqls)
 - [x] Google Tagmanager 4 datalayer implementation
       [docs ↗](https://github.com/graphcommerce-org/graphcommerce/tree/main/packages/googleanalytics)
 - [x] Paypal Express payment service
@@ -49,20 +60,16 @@ The following overview contains the status of items on the GraphCommerce roadmap
 - [x] Checkout payment selection rebuild
 - [x] Core stability (hydratation, caching, query optimization)
 
-## Planned
-
-- [ ] Redesigned cart
-- [ ] Product thumbnail carousel
-- [ ] React Server Components integration
-
 ## Future
 
-- [ ] Fetch Magento image sizes (probe-image-size)
+- [ ] React Server Components integration
+- [ ] Edge runtime for GraphQL Mesh
 - [ ] Windows support
 - [ ] Store locator
 - [ ] Buckaroo payment service
 - [ ] `magento` example without Hygraph
 - [ ] PageBuilder support
+      [depends on ↗](https://github.com/magento/magento2/issues/37768)
 
 ## Next steps
 

package/upgrading/graphcommerce-6-to-7.md

@@ -0,0 +1,96 @@
+# Upgrading from GraphCommerce 6 to 7
+
+Depending on the amounts of customisations you've made, there are some manual
+steps. Please follow the regular [upgrade steps first](./readme.md).
+
+1. [Add `fetchPolicy: cache-first` to LayoutDocument](#add-cache-first-fetchpolicy-to-layoutdocument)
+2. [Use thew new `hygraphPageContent` function instead of DefaultPageQuery](#use-the-new-hygraphpagecontent-function-instead-of-defaultpagequery)
+3. [Translation file updates](#translation-file-updates)
+4. [All @graphql-mesh/\* should be set to latest](#all-graphql-mesh-should-be-set-to-latest)
+5. [Upgrading your Hygraph schema](#upgrading-your-hygraph-schema)
+
+## Add `fetchPolicy: cache-first` to LayoutDocument queries
+
+🟠 Only required if you've added custom pages
+
+All occurences of LayoutDocument should get a `fetchPolicy: 'cache-first'`
+option.
+
+```tsx
+// Find all occurences of
+staticClient.query({ query: LayoutDocument })
+
+// Replace with
+staticClient.query({ query: LayoutDocument, fetchPolicy: 'cache-first' })
+```
+
+## Use the new `hygraphPageContent` function instead of DefaultPageQuery
+
+🟠 Only required if you've added custom pages
+
+The `DefaultPageDocument` is removed in favor of the new `hygraphPageContent`
+query. This function handles caching better and allows for (currently in beta)
+DynamicRows feature.
+
+```tsx
+// DefaultPageDocument
+const page = staticClient.query({
+  query: DefaultPageDocument,
+  variables: { url: `blog/${urlKey}` },
+})
+
+// Becomes hygraphPageContent
+const page = hygraphPageContent(staticClient, `blog/${urlKey}`)
+```
+
+## Translation file updates
+
+🟠 Only required if you've added custom translations
+
+All locales files now require a `msgid` comment. All translations need to have a
+`#. js-lingui-explicit-id` comment added. This could be done with a
+find-and-replace:
+
+Find (including the empty line)
+
+```
+
+msgid
+```
+
+Replace with (including the empty line)
+
+```
+
+#. js-lingui-explicit-id
+msgid
+```
+
+To validate your translations run `yarn lingui` to extract everything.
+
+## All @graphql-mesh/\* should be set to latest.
+
+🟠 Only required if you've added custom @graphql-mesh/\* packages
+
+All @graphql-mesh packages are using a 0.x.x versioning schema. This means that
+each minor change is considered a major change by yarn. This causes lots of
+issues with version mismatches. Since `@graphql-mesh` isn't making any major
+breaking before releasing 1.x this is the safest course of action for now. Once
+1.x is released we'll switch to "^1.0.0" as a version constraint.
+
+In your package.json
+
+```json
+// Replace
+    "@graphql-mesh/json-schema": "^0.37.6",
+    "@graphql-mesh/transform-filter-schema": "^0.15.8",
+
+// With
+    "@graphql-mesh/json-schema": "latest",
+    "@graphql-mesh/transform-filter-schema": "latest",
+```
+
+## Upgrading your Hygraph schema
+
+Upgrade your Hygraph schema with the [Hygraph migration cli](../hygraph/cli.md).
+Select `graphcommerce6to7` as version.

package/upgrading/readme.md

@@ -107,6 +107,7 @@ find . -type f -name '*.rej' -delete
 After resolving the diff issues, manually process upgrade instructions:
 
 - [Upgrading to GraphCommerce 5 to 6](../upgrading/graphcommerce-5-to-6.md)
+- [Upgrading to GraphCommerce 6 to 7](../upgrading/graphcommerce-6-to-7.md)
 
 Run and validate your local environment: