Updating Docs

Author: manifestinteractive

.github/CONTRIBUTING.md

@@ -0,0 +1,29 @@
+![Logo](../docs/img/logo.png "Logo")
+
+Thank you for Contributing
+===
+
+We want to make it as easy as possible to contribute changes.
+
+Follow the requirements below for __[Creating Issues](https://github.com/redvanworkshop/sfcc-cli/issues/new)__ and __[Pull Requests](https://github.com/redvanworkshop/sfcc-cli/pull/new)__, to keep everything simple for everyone :)
+
+<img src="https://octodex.github.com/images/dinotocat.png" width="400" />
+
+Creating an Issue
+---
+
+Use the Prepopulated Template that we provide.  Issues reported that do not use the template will be rejected.
+
+
+Creating a Pull Request
+---
+
+Before you can submit a PR, you will need to:
+
+1. Make a New Branch off of `staging` ( ideally you will name your branch for the issue you are fixing, e,g, `issue-3-fixing-logger` )
+2. Commit & Push your New Branch, with a comment like `Fixes #3` to auto trigger a status change for that issue
+3. Make your Pull Request into the `develop`
+4. Set `Reviewers` and `Assignees` to `Peter Schmalfeldt` ( or other project administrator )
+5. Choose an appropriate label from the `Labels`
+
+Now you can submit a new PR using the Prepopulated Template that we provide.  PR's submitted that do not use the template will be rejected.

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,19 @@
+#### Overview:
+
+_( a detailed overview of the problem this ticket will solve and the targeted audience )_
+
+#### Acceptance Criteria:
+
+_( issue will not be considered complete unless this list of criteria is met, e.g. intended usage, expected functionality, specific metrics met, etc. )_
+
+#### Steps to Duplicate _( required for bug reports )_:
+
+_( a step by step guide written for a person who might be looking at this for the first time )_
+
+#### System Info _( required for bug reports )_:
+
+_( e.g. "MacOS 10.14.2 with ZSH terminal" )_
+
+#### Relevant Documentation _( optional )_
+
+_( e.g. Screenshots, Github Issues, etc )_

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,33 @@
+#### What's this PR do?
+
+_[write_something]_
+
+#### Where should the reviewer start?
+
+_[write_something]_
+
+#### How should this be manually tested?
+
+_[write_something]_
+
+#### Any background context you want to provide?
+
+_[write_something]_
+
+#### What are the relevant github issue?
+
+_[write_something]_
+
+#### Screenshots (if appropriate)
+
+_[drag_and_drop_here]_
+
+#### What gif best describes this PR or how it makes you feel?
+
+_[drag_and_drop_something_fun_here]_
+
+#### Definition of Done:
+
+- [ ] You have actually run this locally and can verify it works
+- [ ] You have verified that `npm test` passes without issue
+- [ ] You have updated the README file (if appropriate)