@graphcommerce/docs 4.2.1 → 4.4.1

package/CHANGELOG.md

@@ -1,5 +1,23 @@
 # Change Log
 
+## 4.4.1
+
+### Patch Changes
+
+- [#1324](https://github.com/graphcommerce-org/graphcommerce/pull/1324) [`73d07c6bb`](https://github.com/graphcommerce-org/graphcommerce/commit/73d07c6bbf630a92e44a2b2baf14200eb6900db5) Thanks [@ErwinOtten](https://github.com/ErwinOtten)! - Update docs, add new graphcms media url
+
+## 4.4.0
+
+### Minor Changes
+
+- [#1320](https://github.com/graphcommerce-org/graphcommerce/pull/1320) [`2ecac6e06`](https://github.com/graphcommerce-org/graphcommerce/commit/2ecac6e06ad19257acfd18e9042c5f81f66b476e) Thanks [@ErwinOtten](https://github.com/ErwinOtten)! - Sort order, add link to create feature request
+
+## 4.3.0
+
+### Minor Changes
+
+- [#1311](https://github.com/graphcommerce-org/graphcommerce/pull/1311) [`af7c45d65`](https://github.com/graphcommerce-org/graphcommerce/commit/af7c45d650c4e1472933ab5393bb370195f3e708) Thanks [@ErwinOtten](https://github.com/ErwinOtten)! - Add contributing
+
 ## 4.2.1
 
 ### Patch Changes

package/contributing.md

@@ -0,0 +1,90 @@
+# Contributing to GraphCommerce
+
+Looking to contribute something to GraphCommerce? Here's how you can help.
+
+Please take a moment to review this document in order to make the contribution
+process easy and effective for everyone involved.
+
+### Bug reports
+
+Well-written, thorough bug reports are a great way to contribute to the project.
+Before raising a new issue, please check our
+[issues list ↗](https://github.com/graphcommerce-org/graphcommerce/issues) to
+determine whether the issue you encountered has already been reported.
+
+A good bug report should be self-explanatory. Use the
+[bug report template ↗](https://github.com/graphcommerce-org/graphcommerce/issues/new/choose)
+to create a bug report.
+
+### Feature requests
+
+Feature requests are welcome. Please take a moment to find out whether your idea
+fits with the scope and aims of the project. It's up to you to make a strong
+case to convince us of the merits of this feature.
+
+Provide as much detail and context as possible. Use the
+[feature request template ↗](https://github.com/graphcommerce-org/graphcommerce/issues/new/choose)
+to create a feature request.
+
+## Pull requests
+
+Good pull requests (e.g. patches, improvements, new features) are a fantastic
+help. Please
+[ask first ↗](https://join.slack.com/t/graphcommerce/shared_invite/zt-11rmgq1ad-F~0daNtKcSvtcC4eQRzjeQ)
+before embarking on any significant pull request (e.g. implementing features or
+refactoring code), otherwise you risk spending a lot of time working on
+something that might not be relevant to the project.
+
+### File structure
+
+```txt
+File structure of GraphCommerce
+
+├── docs
+├── examples
+    └── magento-graphcms
+├── packages
+```
+
+- To make changes to the magento-graphcms template, edit the files in
+  examples/magento-graphcms.
+
+- To modify GraphCommerce framework, components, edit the files in
+  packages/graphcommerce.
+
+- To make changes to the docs, edit the files in docs
+
+### Formatting and Linting
+
+GraphCommerce uses ESLint for linting and Prettier for code formatting. Install
+the [recommended VS Code extensions](../docs/getting-started/vscode.md)
+
+### Contributor License Agreement
+
+Please make sure you have signed our Contributor License Agreement. We are not
+asking you to assign copyright to us, but to give us the right to distribute
+your code without restriction. We ask this of all contributors in order to
+assure our users of the origin and continuing existence of the code. You only
+need to sign the CLA once.
+
+### Creating a pull request
+
+1. Create a pull request. The PR can stay open until you are ready to merge.
+2. Add your changes
+3. Add a changeset
+
+- Run 'yarn changeset' and select minor bump. Commit the changeset that is
+  created.
+
+<figure>
+
+![yarn changeset](https://user-images.githubusercontent.com/1251986/157868337-0fa27e88-cf35-4e38-a59c-72c72ef6b054.jpg)
+
+  <figcaption>Select minor bump when running `yarn changeset`</figcaption>
+</figure>
+
+## Next steps
+
+- Discuss your ideas in the public
+  [ Slack community. ↗](https://join.slack.com/t/graphcommerce/shared_invite/zt-11rmgq1ad-F~0daNtKcSvtcC4eQRzjeQ)
+  chat

package/package.json

@@ -2,7 +2,7 @@
   "name": "@graphcommerce/docs",
   "homepage": "https://www.graphcommerce.org/docs",
   "repository": "github:graphcommerce-org/graphcommerce/docs",
-  "version": "4.2.1",
+  "version": "4.4.1",
   "sideEffects": true,
   "devDependencies": {
     "@graphcommerce/prettier-config-pwa": "^4.0.2"

package/readme.md

@@ -1,6 +1,6 @@
 ---
 menu: Overview
-order: getting-started,framework
+order: getting-started,framework, contributing, roadmap
 metaTitle: Start React, Next.js Magento PWA development here - GraphCommerce
 metaDescription:
   'GraphCommerce is the open-source PWA Studio Magento 2 alternative.