diff --git a/DEVELOPERS.md b/DEVELOPERS.md
new file mode 100644
index 00000000..8e9da9ce
--- /dev/null
+++ b/DEVELOPERS.md
@@ -0,0 +1,190 @@
+# Developer Guide for contributing to MyParcel repositories
+
+This document is a guide for developers who want to contribute to MyParcel repositories. It contains information about the development process, how to create a pull request and how to write a good commit message.
+
+## Pull requests
+
+- A pull request should contain a single feature or bug fix.
+- A pull request should be as small as possible. This makes it easier to review and merge.
+- The title and description of the pull request must comply with the rules in [Commit messages](#commit-messages).
+
+## Commit messages
+
+We use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) to standardize our commit messages. This makes it easier to generate changelogs and release notes.
+
+Read the [conventional commit specification](https://www.conventionalcommits.org/en/v1.0.0/#specification) for in-depth information about the commit message format.
+
+Most of what is written in the specification is also explained in the following sections.
+
+### Anatomy of a commit message
+
+```text
+<type>(<scope>): <subject>
+<BLANK LINE>
+<body>
+<BLANK LINE>
+<footer>
+```
+
+**Required:**
+
+- `type`: The type of commit. See [Types](#types).
+- `subject`: The subject of the commit. This is a short description of the commit. It should not contain more than 50 characters.
+
+**Optional:**
+
+- `scope`: The scope of the commit. This is the part of the code that is affected by the commit. For example: `api`, `webhook`, `frontend`, `backend`, `cli`, `docs`, `tests`, etc. This can be omitted if the scope is not relevant. The value of the scope depends on the project you're working on.
+- `body`: The body of the commit. This is a longer description of the commit. It can contain multiple lines. Capitalization is allowed.
+- `footer`: The footer of the commit. This is used to reference issues. For example: `Closes #123`, `Closes #123, Closes #456, ...`. Capitalization is allowed.
+
+### Rules
+
+- Use the imperative mood in the subject line.
+- Do not capitalize the subject line.
+- Do not end the subject line with a period.
+- Use the body to explain the "what" and "why" of the commit, not the "how".
+- If the commit fixes an issue, add "Closes #issue-number" to the body.
+  - In case there are multiple issues, add "Closes #issue-number, Closes #issue-number, ..." to the body.
+
+The header of your commit should be your pull request title, and the body should be your pull request description.
+
+### Types
+
+In the commit message, the type is the first word in the subject line. It is followed by a colon and a space. The type can be one of the following:
+
+- `feat`: A new feature.
+- `fix`: A bug fix.
+- `perf`: A change that improves performance but does not affect the meaning of the code.
+- `style`: A change that does not affect the meaning of the code. For example: formatting, adding missing semicolons, automatic fixes by linters, etc.
+- `refactor`: A change that neither fixes a bug nor adds a feature. For example: renaming a variable, moving a function, etc.
+- `build`: A change that affects the build process, e.g. changing the build tool, updating GitHub actions workflows, changing scripts in `package.json`, etc.
+- `chore`: A change that does not affect the meaning of the code. For example: updating `.gitignore`, `.github/CODEOWNERS`, `LICENSE` etc.
+- `docs`: A change that only affects documentation, e.g. README.md, CONTRIBUTING.md, etc.
+
+#### Flowchart
+
+Here's a flowchart to help you decide on what type you should use in your commit message.
+
+```mermaid
+%%{ init: { 'flowchart': { 'curve': 'linear' } } }%%
+graph TD
+  classDef start fill:#bada55,stroke:#1aa,stroke-width:4px,color:#000;
+  classDef finish fill:#10622A,stroke:#14923D,stroke-width:3px,color:#fff;
+
+  Start{"Start"}:::start
+  
+  Feat(["feat"]):::finish
+  Fix(["fix"]):::finish
+  Perf(["perf"]):::finish
+  Refactor(["refactor"]):::finish
+  Style(["style"]):::finish
+  Build(["build"]):::finish
+  Docs(["docs"]):::finish
+  Chore(["chore"]):::finish
+  Test(["test"]):::finish
+
+  QProdCode{{"Does this change production code?\n(e.g. code in the `src` directory)"}}
+  QFunctionalChange{{"Does this change functionality for the end user?"}}
+  QIsFix{{"Is this something that has worked before?"}}
+  QIsBuild{{"Is this change related to the build process?"}}
+  QIsPerf{{"Does this improve performance?"}}
+  QIsRefactor{{"Is code refactored?\n(e.g. renaming or moving variables, etc.)"}}
+  QIsDoc{{"Is this a documentation change?"}}
+  QIsTest{{"Is this a change in test code?"}}
+
+  Start .->  QProdCode
+
+  QProdCode --> |Yes| QFunctionalChange
+  QProdCode ------> |No| QIsTest
+
+  QIsTest --> |Yes| Test
+  QIsTest --> |No| QIsBuild
+
+  QFunctionalChange --> |Yes| QIsFix
+  QFunctionalChange --> |No| QIsPerf
+  
+  QIsFix --> |Yes| Fix
+  QIsFix --> |No| Feat
+  
+  QIsBuild --> |Yes| Build
+  QIsBuild --> |No| QIsDoc
+  
+  QIsDoc --> |Yes| Docs
+  QIsDoc --> |No| Chore
+  
+  QIsPerf --> |Yes| Perf
+  QIsPerf --> |No| QIsRefactor
+  
+  QIsRefactor --> |Yes| Refactor
+  QIsRefactor --> |No| Style
+```
+
+### Correct examples
+
+#### ✅ Simple commit
+
+```text
+feat: add new feature
+```
+
+#### ✅ With scope
+
+```text
+feat(api): add new feature
+```
+
+#### ✅ With body and footer
+
+```text
+feat: add new feature
+
+This is a longer description of the feature. It can contain multiple lines.
+
+Closes #123
+```
+
+### Incorrect examples
+
+#### ❌ Capitalized subject
+
+```text
+Feat: add new feature
+```
+
+#### ❌ Subject ending with a period
+
+```text
+feat: add new feature.
+```
+
+#### ❌ Subject line too long
+
+```text
+feat: add new feature that is longer than 50 characters
+```
+
+#### ❌ Subject not in imperative mood
+
+```text
+feat: new feature
+```
+
+```text
+feat: added new feature
+```
+
+#### ❌ Body not separated from header
+
+```text
+feat: add new feature
+This is a longer description of the feature. It can contain multiple lines.
+```
+
+#### ❌ Body not separated from footer
+
+```text
+feat: add new feature
+
+This is a longer description of the feature. It can contain multiple lines.
+Closes #123
+```
