Updating information for Contributors

CONTRIBUTING.md

@@ -4,9 +4,27 @@
 
 <em lang="de">Die <a href="#deutsch">deutsche Übersetzung</a> findest du weiter unten.</em>
 
-## English
-
-### [Code of conduct](https://www.ecamp3.ch/en/code-of-conduct)
+# English
+
+## [Code of conduct](https://www.ecamp3.ch/en/code-of-conduct)
+
+## Workflow
+This is a basic Overview of the Workflow, more Information about how to set up a development environment on your Computer is in the [Wiki](https://github.com/ecamp/ecamp3/wiki/installation).
+If something about the setup is unclear or you run into an error, there are [discussions](https://github.com/ecamp/ecamp3/discussions) on GitHub for you to ask questions and ask for help.
+### Labels
+Issues are Marked with Labels and some of them are not self-explanatory and explained here:
+- **Type-Labels**:
+Type labels follow the `type: *` format with the options `Frontend`, `Print`, `Deployment` & `API` the architecture for those are partially Documented in the [Wiki](https://github.com/ecamp/ecamp3/wiki/architecture-frontend)
+- **Needs prototype**: This Issue needs a Prototype first, don't start fully implementing this Feature yet. A Prototype can be many things, if your Prototype is an Sketch, Mockup, Partial Implementation or something else is up to you.
+- **Good first issue**: Beginner friendly Issues.
+- **Feature request**: A Idea/Request for a Functionality, not Ready to be Implemented but ready to be discussed.
+
+### Starting an Issue
+Find an Issue that appeals to you, if you are new try a [Good First Issue](https://github.com/ecamp/ecamp3/labels/Good%20first%20issue).
+Not all Issues are ready to be implemented, another helpful Label is [Ready for Implementation](https://github.com/ecamp/ecamp3/issues?q=is%3Aopen+is%3Aissue+label%3A%22Ready+for+implementation%22): Those issues should be specified enough to understand the idea/requirement of the issue, but what matters is that you understand the Issue so don't hesitate to ask questions.
+If you found an Issue we recommend to leave a comment on Issue, and we will assign you. This is to make sure the specifications of the Issue you are working on are still up-to-date and there aren't two people working on the same Issue. 
+As an Alternative you can open a Draft PR to let everyone know you are working on that issue.
+The Wiki should help you understand the project better but its imperfect, if something is unclear leave a comment in the Issue.
 
 ### Git setup
 
@@ -36,7 +54,7 @@ We use a triangular git workflow. This means that all changes are first pushed t
 
 Once this is set up, you can start coding, and all `git pull` commands should pull from the central repository by default, while all `git push` commands will push to your fork of the project.
 
-### Starting a new feature
+#### Checkout a Featurebranch
 
 Before starting a new feature, you should do the following steps to start with a clean state that is easily mergeable later: