Update CHANGELOG and CONTRIBUTING

Author: spencerfinnell

CHANGELOG.md

@@ -1,3 +1,23 @@
+## [2.2.0] - 2018-12-20
+
+### New
+
+- Accessibility improvements:
+  - Better tabbing order for shop filters and results.
+  - "Skip to content" and "Skip to result" skip links.
+  - Ensure all focus outlines are visible.
+- Upgrade developer experience:
+  - Use more `@wordpress` `npm` packages (`eslint`, `browserslist`)
+  - Update JS coding standards.
+  - Update PHP coding standards.
+  - Update CSS coding standards.
+- Request a Google Fonts API key when generating font list.
+- Allow integrations to define helper files to be autoloaded.
+
+### Fix
+
+- Avoid error if offcanvas drawer source or target does not exist.
+
 ## [2.1.0] - 2018-12-18
 
 ### New
@@ -9,7 +29,7 @@
 ### Fix
 
 - Ensure button color is accurately reflected.
-- Coding standad updates.
+- Coding standard updates.
 
 ## [2.0.0] - 2018-11-06
 

CONTRIBUTING.md

@@ -2,15 +2,15 @@
 
 ## Getting Started
 
-If you prefer to set things up manually, be sure to have <a href="https://nodejs.org/en/">Node.js installed first</a>. You should be running a Node version matching the [current active LTS release](https://github.com/nodejs/Release#release-schedule) or newer for this plugin to work correctly. You can check your Node.js version by typing `node -v` in the Terminal prompt.
+Be sure to have <a href="https://nodejs.org/en/">Node.js installed first</a>. You should be running a Node version matching the [current active LTS release](https://github.com/nodejs/Release#release-schedule) or newer for this plugin to work correctly. You can check your Node.js version by typing `node -v` in the Terminal prompt.
 
 You should also have the latest release of <a href="https://npmjs.org">npm installed</a>, npm is a separate project from Node.js and is updated frequently. If you've just installed Node.js which includes a version of npm within the installation you most likely will need to also update your npm install. To update npm, type this into your terminal: `npm install npm@latest -g`
 
 To test the plugin, or to contribute to it, you can clone this repository and build the plugin files using Node. How you do that depends on whether you're developing locally or uploading the plugin to a remote host.
 
 ### Local Environment
 
-Next, open a terminal (or if on Windows, a command prompt) and navigate to the repository you cloned. Now type `npm run setup-theme` to get the dependencies all set up. Then you can type `npm run dev` in your terminal or command prompt to keep the theme building in the background as you work on it.
+Next, open a terminal (or if on Windows, a command prompt) and navigate to the repository you cloned. Now type `npm run setup-theme-dev` to get the dependencies all set up. Then you can type `npm run dev` in your terminal or command prompt to keep the theme building in the background as you work on it.
 
 ## Workflow
 
@@ -21,10 +21,11 @@ A good workflow for new contributors to follow is listed below:
 - Make code changes
 - Commit code changes within newly created branch
 - Push branch to forked repository
-- Submit Pull Request to `bigbox-theme` repository
+- Submit Pull Request to `bigbox` repository
 
 Ideally name your branches with prefixes and descriptions, like this: `[type]/[change]`. A good prefix would be:
 
 - `add/` = add a new feature
 - `try/` = experimental feature, "tentatively add"
-- `update/` = update an existing feature
+- `update/` = update an existing feature
+- `issue/` = solve an open issue