@graphcommerce/docs 6.0.2-canary.9 → 6.1.1-canary.0

package/CHANGELOG.md

@@ -1,5 +1,39 @@
 # Change Log
 
+## 6.1.1-canary.0
+
+## 6.1.0
+
+### Patch Changes
+
+- [#1876](https://github.com/graphcommerce-org/graphcommerce/pull/1876) [`8dffc59c0`](https://github.com/graphcommerce-org/graphcommerce/commit/8dffc59c04bf6f2a6000b73db13592e10afd936c) - Added an configuration `wishlistShowFeedbackMessage` to show a feedback message when a product is added to the wishlist. ([@paales](https://github.com/paales))
+
+## 6.0.2-canary.22
+
+## 6.0.2-canary.21
+
+## 6.0.2-canary.20
+
+## 6.0.2-canary.19
+
+## 6.0.2-canary.18
+
+## 6.0.2-canary.17
+
+## 6.0.2-canary.16
+
+## 6.0.2-canary.15
+
+## 6.0.2-canary.14
+
+## 6.0.2-canary.13
+
+## 6.0.2-canary.12
+
+## 6.0.2-canary.11
+
+## 6.0.2-canary.10
+
 ## 6.0.2-canary.9
 
 ## 6.0.2-canary.8

package/framework/config.md

@@ -189,7 +189,7 @@ Hide the wishlist functionality for guests.
 
 #### `wishlistIgnoreProductWishlistStatus: Boolean`
 
-Ignores wether a product is already in the wishlist, makes the toggle an add only.
+Ignores whether a product is already in the wishlist, makes the toggle an add only.
 
 #### `wishlistShowFeedbackMessage: Boolean`
 

package/framework/graphcms.md

@@ -19,9 +19,10 @@ by adding Hygraph content to pages.
 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:
+as your starting point. Update the variable in the `/graphcommerce.config.js`
+file:
 
-`GRAPHCMS_URL=""`  
+`hygraphEndpoint: ''`  
 Hygraph API URL. Once logged in, copy it from Project Settings > Api Access >
 Content API
 

package/framework/plugins-graphql.md

@@ -1,7 +1,7 @@
 # Plugins GraphQL
 
 GraphCommerce's GraphQL plugin system allows you to extend GraphCommerce in a
-plug-and-play manner. Install a new package and the queries will be exdtended at
+plug-and-play manner. Install a new package and the queries will be extended at
 the right places.
 
 ## What problem are we solving?

package/framework/plugins-react.md

@@ -1,7 +1,7 @@
 # Plugins React
 
-GraphCommerce's React plugin system allows you to extend GraphCommerce's build
-in components with your own logic.
+GraphCommerce's React plugin system allows you to extend GraphCommerce's
+built-in components with your own logic.
 
 - No runtime overhead: The plugin system is fully implemented in webpack and
 - Easy plugin creation: Configuration should happen in the plugin file, not a
@@ -18,8 +18,8 @@ no performance penalty.
 
 ## How do I write a plugin?
 
-In this example we're going to add a 'BY GC' text to list items, as can seen on
-the demo on
+In this example we're going to add some text to list items, just like the text
+‘BY GC’ that can seen in the demo on
 [category pages](https://graphcommerce.vercel.app/nl/women/business).
 
 1. Create a new file in `/plugins/ProductListItemByGC.tsx` with the following
@@ -119,7 +119,7 @@ The Webpack plugin statically analyses the plugin file to find `component`,
 
 ### Possible use cases
 
-In the examples above we've extended the payment methods, but it should also
+In the examples above we've extended the product list items, but it should also
 work for other things such as:
 
 - Googletagmanager
@@ -133,7 +133,7 @@ work for other things such as:
 ### Conditionally include a plugin
 
 Provide an ifConfig export in the plugin that will only include the plugin if a
-[configuration](./config.md) value is truety.
+[configuration](./config.md) value is truthy.
 
 ```tsx
 import type { IfConfig } from '@graphcommerce/next-config'

package/framework/theming.md

@@ -34,7 +34,7 @@ and text colors. Save the file to see your changes updated in real-time:
   },
 ```
 
-You can search through your codebase to discover which component will be
+You can search through your codebase to discover which components will be
 affected by your changes. For example, search for occurrences of
 `theme.palette.primary.main`.
 
@@ -62,7 +62,7 @@ Most components have props that define their look and feel. Most common are the
   [MUI Button documentation ↗](https://mui.com/components/buttons/)
 - To learn which options are accepted by a prop, refer to the component's API:
   [MUI Button API ↗](https://mui.com/api/button/). You can also use your IDE's
-  suggestions functionality. For [VS Code's](../getting-started/vscode.md)
+  suggestions functionality. For [VS Code's](../framework/vscode.md)
   IntelliSense feature, type Ctrl+Space.
 - It can be helpful to learn how a component is styled, for example, to explore
   how palette variables are used. Refer to the
@@ -145,7 +145,7 @@ To overwrite a component's hover state, add the sx prop:
 <Button
   color='primary'
   variant='contained'
-  sx={{ '&&:hover': { background: 'green' } }}
+  sx={{ '&:hover': { background: 'green' } }}
 >
   <Trans>Contact Us</Trans>
 </Button>

package/getting-started/pages.md

@@ -32,7 +32,7 @@ frontend React framework that uses Next.js for server-side rendering.
 
 ### Create the route
 
-- Create a new file, /about/about-us.tsx:
+- Create a new file, /pages/about/about-us.tsx:
 
 ```tsx
 export default function AboutUs() {

package/package.json

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

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

@@ -11,7 +11,7 @@ regular [upgrade steps first](./readme.md).
 ## Migrating to graphcommerce.config.js
 
 GraphCommerce 6 uses a new [configuration file](../framework/config.md) called
-`graphcommerce.config.js` this replaces the current configuration. When staring
+`graphcommerce.config.js` this replaces the current configuration. When starting
 a dev server, GraphCommerce will notify you how to migrate your env variables to
 graphcommerce.config.js.
 

package/upgrading/readme.md

@@ -80,7 +80,7 @@ packages:
 
 ### Resolving diff issues
 
-When you run `git apply ...` (step 4), git will try and apply all the diffs from
+When you run `git apply ...` (step 5), git will try and apply all the diffs from
 the patch file to your project files. When applying a diff fails, a
 [reject ↗](https://git-scm.com/docs/git-apply#Documentation/git-apply.txt---reject)
 `.rej` file will be created for _each_ file that could not be upgraded.