Updating contribution guides for docs.

Author: dobooth

.github/CONTRIBUTING.md

@@ -40,7 +40,7 @@ All contributors are required to submit a click-through form to agree to the ter
 
    - Unit/integration test coverage
    - Proposed documentation update.
-     For the documentation contribution guidelines, see [DevDocs Contributing][devdocs].
+     For the documentation contribution guidelines, see [DOCUMENTATION_TEMPLATE][].
 7. For large features or changes, [open an issue][issue] to discuss first.
    This may prevent duplicate or unnecessary effort, and it may gain you some additional contributors.
 8. To report a bug, [open an issue][issue], and follow [guidelines about bugfix issues][issue reporting].
@@ -160,7 +160,7 @@ Label| Description
 [create issue]: https://help.github.com/articles/creating-an-issue/
 [create pr]: https://help.github.com/articles/creating-a-pull-request/
 [Definition of Done]: https://devdocs.magento.com/guides/v2.2/contributor-guide/contributing_dod.html
-[devdocs]: https://github.com/magento/devdocs/blob/master/.github/CONTRIBUTING.html
+[DOCUMENTATION_TEMPLATE]: https://github.com/magento/devdocs/blob/master/.github/CONTRIBUTING.html
 [existing issues]: https://github.com/magento/magento2-functional-testing-framework/issues?q=is%3Aopen+is%3Aissue
 [existing PRs]: https://github.com/magento/magento2-functional-testing-framework/pulls?q=is%3Aopen+is%3Apr
 [GitHub documentation]: https://help.github.com/articles/syncing-a-fork

.github/DOCUMENTATION_TEMPLATE.md

@@ -0,0 +1,64 @@
+# How to conttribute to MFTF docs
+
+MFTF documentation is kept within the /docs/ folder in this repo.
+We welcome contributions to the documentation.
+This page describes the process for submitting docs and serves as a template so that docs are written properly.
+
+The contribution workflow for docs is the same as submitting code.
+To contribute to MFTF docs:
+
+1. Make a branch from the [MFTF repo][].
+1. Make edits/additions/deletions as needed.
+1. Submit your PR to the `develop` branch.
+
+Once submitted, it will be reviewed by a member of the documentation team.
+If approved it will be tested and merged.
+If it needs any work, we will inform you.
+
+Any changes to the Table of Contents will need to be made in the regular [devdocs repo][].
+
+## H2 heading - blank line before and after, capitalize first word only
+
+1. Ordered lists all all numbered 1.
+1. The build process will number them correctly.
+1. Single spafce after the number. Blank line before and after list.
+
+### H3
+
+- Unordered lists use dashes.
+- One space after the dash.
+- Blank line before and after list.
+
+## Code Samples
+
+For formatting and code coloring, wrap code samples in the following format.
+Replace the `xml` with the file extension of the code sample type. Use `bash` for command-line text.
+
+```xml
+<xmlSample>
+   ...
+   ...
+</xmlSample>
+```
+
+## Markdown tables
+
+| Header      | Header |
+| ----------- | ----------- |
+| Colume 1 text | Column 2 text|
+| Column 1 text | Column 2 text|
+
+Markdown tables work for simple tables. If you need lists or other complex features within a cell, you may have to use a HTML table.
+
+## Other tips
+
+- Use spaces instead of tabs.
+- One empty line between content. No duplicate empty lines.
+- Read more about how to [Contribute to Magento Devdocs][]
+
+<!-- For readability, we abstract the link URLS to the bottom of the page. The extra set of square brackets denotes it is a link, rather than plain brackets. >
+
+<!-- Link Definitions -->
+[devdocs repo]: https://github.com/magento/devdocs
+[MFTF repo]: https://github.com/magento/magento2-functional-testing-framework
+[Contribute to Magento Devdocs]: https://github.com/magento/devdocs/blob/master/.github/CONTRIBUTING.md