Merge branch 'dev' into fix-uikitworkshop-absolutely-positioned-pattern-parts-at-the-vertical-end-of-the-page-would-get-cropped

Author: mfranzke

.github/CONTRIBUTING.md

@@ -18,7 +18,7 @@ nvm use <<version>>
 The best way to make changes to the Pattern Lab Node core and test them is through an edition.
 
 * Fork this repository on Github.
-* `npm install && npm run bootstrap`
+* `yarn install && yarn run bootstrap`
 * Create a new branch in your fork and push your changes in that fork.
 * `cd packages/edition-node`
 * Test your changes with the edition's api
@@ -28,7 +28,7 @@ The best way to make changes to the Pattern Lab Node core and test them is throu
 To ensure that developers can bootstrap the repo from a fresh clone, do this in your working copy:
 
 ```sh
-git reset --hard && git clean -dfx && npm install && npm run bootstrap
+git reset --hard && git clean -dfx && yarn install && yarn run bootstrap
 ```
 
 This ensures that any changes you've made will still result in a clean and functional developer experience. **Note**: be sure you've committed any outstanding work before doing this -- it will blow away whatever's still outstanding, including anything staged but not commited.
@@ -37,6 +37,7 @@ This ensures that any changes you've made will still result in a clean and funct
 
 * _ALWAYS_ submit pull requests against the [dev branch](https://github.com/pattern-lab/patternlab-node/tree/dev). If this does not occur, I will first, try to redirect you gently, second, attempt to redirect the target branch myself, thirdly, port over your contribution manually if time allows, and/or lastly, close your pull request. If you have a major feature to stabilize over time, talk to @bmuenzenmeyer via an issue about making a dedicated `feature-branch`
 * Keep your pull requests concise and limited to **ONE** substantive change at a time. This makes reviewing and testing so much easier.
+* If it takes you considerable time to finish your work, submit a [draft pull request](https://github.blog/2019-02-14-introducing-draft-pull-requests/). This is Github's way to indicate work in progress but allows for feedback.
 * Commits should reference the issue you are adressing. For any Pull Request that you send, use the template provided.
 * Commits are best formatted using the [conventional commits pattern](https://conventionalcommits.org/).
 * If you can, add some unit tests using the existing patterns in the `.packages/core/test` directory

packages/docs/src/support.md

@@ -9,4 +9,4 @@ title: Pattern Lab Support
 
 ## Gitter
 
-You can head over to [Pattern Lab's Gitter](https://gitter.im/pattern-lab/home) to chat with the Pattern Lab community. This is a great place to talk shop, ask quesitons, and get (and give!) help.
+You can head over to [Pattern Lab's Gitter](https://gitter.im/pattern-lab/home) to chat with the Pattern Lab community. This is a great place to talk shop, ask questions, and get (and give!) help.