@graphcommerce/docs 8.0.1 → 8.0.2-canary.0

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Change Log
 
+## 8.0.2-canary.0
+
+### Patch Changes
+
+- [#2195](https://github.com/graphcommerce-org/graphcommerce/pull/2195) [`207cd41`](https://github.com/graphcommerce-org/graphcommerce/commit/207cd4147621e53353b0b354c80d575df78089f0) - Documentation on multistore setup added
+  ([@paales](https://github.com/paales))
+
 ## 8.0.1
 
 ### Patch Changes

package/framework/config.md

@@ -334,7 +334,9 @@ All storefront configuration for the project
 
 #### locale: string (required)
 
-Must be a locale string https://www.unicode.org/reports/tr35/tr35-59/tr35.html#Identifiers
+Must be a [locale string](https://www.unicode.org/reports/tr35/tr35-59/tr35.html#Identifiers) for automatic redirects to work.
+
+This value can be used as a sub-path identifier only, make sure linguiLocale is configured for each URL.
 
 #### magentoStoreCode: string (required)
 
@@ -390,7 +392,9 @@ 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. Must be lowercase valid locale.
+
+This value is also used for the Intl.
 
 ### MagentoConfigurableVariantValues
 

package/framework/translations.md

@@ -215,6 +215,10 @@ msgstr ""
 > suggestions in VS Code with the
 > [Github copilot extention ↗](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot).
 
+## Use country specific locales like `en-us` and `en-gb`
+
+Configure `linguiLocale` in the storefront config.
+
 ## Next steps
 
 - Learn more about

package/magento/multi-store-language-and-website.md

@@ -0,0 +1,100 @@
+# Multi store, language and website setup
+
+GraphCommerce builds on top of the
+[Next.js internationalization feature](https://nextjs.org/docs/pages/building-your-application/routing/internationalization#getting-started).
+
+## Sub-path routing
+
+Locales are UTS Locale Identifiers, a standardized format for defining locales.
+
+Generally a Locale Identifier is made up of a language, region, and script
+separated by a dash: `language-region-script`. The region and script are
+optional. An example how to configure it in GraphCommerce:
+
+```js
+const config = {
+  storefront: [
+    { locale: 'en-US', defaultLocale: true },
+    { locale: 'nl-NL' },
+    { locale: 'de' },
+  ],
+}
+```
+
+This will result in the following URLs:
+
+- `https://www.graphcommerce.org/some-path/here`
+- `https://www.graphcommerce.org/nl-NL/some-path/here`
+- `https://www.graphcommerce.org/de/some-path/here`
+
+## Domain routing
+
+The domains can be subdomains or top-level domains. The configuration is the
+same for both.
+
+```js
+const config = {
+  storefront: [
+    { domain: 'www.graphcommerce.org', locale: 'en-US', defaultLocale: true },
+    { domain: 'www.graphcommerce.org', locale: 'fr' },
+    { domain: 'www.graphcommerce.nl', locale: 'nl-NL' },
+    { domain: 'de.graphcommerce.org', locale: 'de-DE' },
+  ],
+}
+```
+
+This will result in the following URLs:
+
+- `https://www.graphcommerce.org/some-path/here`
+- `https://www.graphcommerce.org/fr/some-path/here`
+- `https://www.graphcommerce.nl/some-path/here`
+- `https://de.graphcommerce.org/some-path/here`
+
+## Domain routing + same locale
+
+Next.js does not allow reusing locales (even if it is on different domains), to
+work around this, we're using the fact that a locale is allowed to have a
+'script' value in the format: `language-region-script`. We use this part to
+differentiate between the same locales on different domains.
+
+Configuring the `linguiLocale` makes sure the correct translation file is loaded
+here.
+
+```js
+const config = {
+  storefront: [
+    { domain: 'domain1.com', locale: 'en-us-domain1', linguiLocale: 'en' },
+    { domain: 'domain2.com', locale: 'en-us-domain2', linguiLocale: 'en' },
+    { domain: 'domain3.com', locale: 'en-us-domain3', linguiLocale: 'en' },
+  ],
+}
+```
+
+### Separating Sub-paths from locales
+
+Note: Available from GraphCommerce 8.1.0
+
+Warning: Separating paths form locales will break Next.js' automatic redirect
+functionality.
+
+```js
+const config = {
+  storefront: [
+    { locale: 'default', linguiLocale: 'en', defaultLocale: true },
+    { locale: 'fr_fr', linguiLocale: 'fr' },
+    { locale: 'nl_nl', linguiLocale: 'nl' },
+  ],
+}
+```
+
+This will result in the following URLs:
+
+- `https://www.graphcommerce.org/some-path/here`
+- `https://www.graphcommerce.org/fr_fr/some-path/here`
+- `https://www.graphcommerce.org/nl_nl/some-path/here`
+
+## Further reading
+
+- [Next.js docs: Prefixing the default locale](https://nextjs.org/docs/pages/building-your-application/routing/internationalization#prefixing-the-default-locale)
+- [Next.js docs: Sub-path routing](https://nextjs.org/docs/pages/building-your-application/routing/internationalization#sub-path-routing).
+- [Next.js docs: Domain routing](https://nextjs.org/docs/pages/building-your-application/routing/internationalization#domain-routing)

package/package.json

@@ -2,10 +2,10 @@
   "name": "@graphcommerce/docs",
   "homepage": "https://www.graphcommerce.org/docs",
   "repository": "github:graphcommerce-org/graphcommerce/docs",
-  "version": "8.0.1",
+  "version": "8.0.2-canary.0",
   "sideEffects": true,
   "peerDependencies": {
-    "@graphcommerce/prettier-config-pwa": "^8.0.1"
+    "@graphcommerce/prettier-config-pwa": "^8.0.2-canary.0"
   },
   "prettier": "@graphcommerce/prettier-config-pwa"
 }