| This PR mostly adds the boilerplate kind of documentation you would expect.
- License
- Code of Conduct
- Multiple Issue Templates (bug report, feature request, ask for help)
- Pull Request Template
- Code Owners
- Top level contributing guide that links to various different guides
- Various guides for opening issues, PRs, examples etc.
- Tidies up the Readme to point to other docs.
There is one major feature of this PR. It introduces a *commit message guideline*. I ask everyone that reviews this PR to please take a close look at these guidelines added in the Pull Requests guide. Overall, the commit message guidelines are very simple to follow, and they provide a lot of value.
- Commit messages are more readable, especially when looking through the *project history*.
- Commit messages to describe whether a major, minor or patch change has been introduced (see [semver.org](https://semver.org/)).
- Commit messages can be used to generate a changelog.
|