chore: add README.md and CONTRIBUTING.md (#58)

Author: skyfrk

.github/CONTRIBUTING.md

@@ -0,0 +1,48 @@
+# How to contribute
+
+Thank you for investing your time in contributing to our project! Any contribution you make will be reflected on [developer.tapio.one](https://developer.tapio.one) ✨.
+
+Read our [Code of Conduct](./CODE_OF_CONDUCT.md) to keep our community approachable and respectable.
+
+In this guide you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR.
+
+## New contributor guide
+
+To get an overview of the project, read the [README](README.md). Here are some resources to help you get started with open source contributions:
+
+- [Finding ways to contribute to open source on GitHub](https://docs.github.com/en/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github)
+- [Set up Git](https://docs.github.com/en/get-started/quickstart/set-up-git)
+- [GitHub flow](https://docs.github.com/en/get-started/quickstart/github-flow)
+- [Collaborating with pull requests](https://docs.github.com/en/github/collaborating-with-pull-requests)
+
+## Issues
+
+### Create a new issue
+
+If you spot a problem with the docs, [search if an issue already exists](https://github.com/tapioone/docs/issues). If a related issue doesn't exist, you can open a new issue.
+
+### Solve an issue
+
+Scan through our [existing issues](https://github.com/tapioone/docs/issues) to find one that interests you. If you find an issue to work on, you are welcome to open a PR with a fix!
+
+#### Make Changes
+
+1. Install the correct node version (see `package.json`).
+2. Clone the repository `git clone https://github.com/tapioone/docs.git`.
+3. Install all dependencies `npm install`.
+4. Start the development server `npm run start`.
+5. Make your changes.
+
+#### Commit your update
+
+Commit the changes once you are happy with them. Please adhere to the [conventional commits standard](https://www.conventionalcommits.org/en/v1.0.0/) for naming your commits.
+
+#### Pull Request
+
+When you're finished with the changes, create a pull request, also known as a PR.
+
+- Don't forget to [link your PR to an issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) if you are solving one.
+- Once you submit your PR, a friendly bot will kindly ask you to sign our [CLA](https://github.com/tapioone/cla).
+- We may ask for changes to be made before a PR can be merged, either using [suggested changes](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request) or pull request comments. You can apply suggested changes directly through the UI. You can make any other changes in your fork, then commit them to your branch.
+- As you update your PR and apply changes, mark each conversation as [resolved](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#resolving-conversations).
+- If you run into any merge issues, checkout this [git tutorial](https://github.com/skills/resolve-merge-conflicts) to help you resolve merge conflicts and other issues.

.github/SECURITY.md

@@ -4,6 +4,6 @@
 
 The tapio team takes security bugs seriously. We appreciate your efforts to responsibly disclose your findings!
 
-To report a security issue, **DO NOT** open a GitHub issue, but send us an email to [info@tapio.one](mailto:info@tapio.one?subject=SECURITY) including the word `SECURITY` in the subject line.
+To report a security issue, **DO NOT** open a GitHub issue, but send us an email to [developer@tapio.one](mailto:developer@tapio.one?subject=SECURITY) including the word `SECURITY` in the subject line.
 
 The tapio team will send a response indicating the next steps in handling your report. After the initial reply to your report, the team will keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.

README.md

@@ -0,0 +1,55 @@
+<div align=center>
+
+<h1>tapio docs</h1>
+
+</div>
+
+This repository contains the documentation website code and Markdown source files for [developer.tapio.one](https://developer.tapio.one).
+
+tapio is the digital ecosystem for the woodworking industry. It enables both small carpenters and industrial furniture productions to digitalize their production in a short period of time. It even allows third party developers to implement new solutions, based on the data of tapio-connected machines.
+
+## Run Locally
+
+Clone the project
+
+```bash
+git clone https://github.com/tapioone/docs.git
+```
+
+Go to the project directory
+
+```bash
+cd docs
+```
+
+Install dependencies
+
+```bash
+npm install
+```
+
+Start the server
+
+```bash
+npm run start
+```
+
+## Contributing
+
+Contributions are always welcome!
+
+See [CONTRIBUTING.md](./.github/CONTRIBUTING.md) for ways to get started.
+
+Please adhere to our [code of conduct](./.github/CODE_OF_CONDUCT.md).
+
+## Feedback
+
+If you have any feedback, please reach out to us at [email protected]
+
+## Security
+
+The tapio team takes security bugs seriously. We appreciate your efforts to responsibly disclose your findings! Please refer to our [security policy](./.github/SECURITY.md).
+
+## License
+
+[MIT](./LICENSE)