diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 56ef8a0d..43893d9f 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,51 +1,328 @@
# Contributing to KeeWeb
-Thanks for taking the time to contribute! :gift:
+Thank you for your interest in contributing to KeeWeb! :gift:
-There are different ways to help the project, you will find a summary here.
+Below are a list of ways that you can help contribute to this project, as well as policies and guides that explain how to get started.
-## Code of conduct
+Please review everything on this page before you submit your contribution.
+
+
+
+- [Contributing to KeeWeb](#contributing-to-keeweb)
+ - [Code of Conduct](#code-of-conduct)
+ - [Issues, Bugs, Ideas](#issues-bugs-ideas)
+ - [Vulnerabilities](#vulnerabilities)
+ - [Development](#development)
+ - [Before Submitting Pull Requests](#before-submitting-pull-requests)
+ - [Conventional Commit Specification](#conventional-commit-specification)
+ - [Types](#types)
+ - [Example 1:](#example-1)
+ - [Example 2:](#example-2)
+ - [Referencing Issues](#referencing-issues)
+ - [Commenting](#commenting)
+ - [Variable \& Method Casing](#variable--method-casing)
+ - [ESLint \& Prettier](#eslint--prettier)
+ - [Spaces Instead Of Tabs](#spaces-instead-of-tabs)
+ - [Documentation / Wiki](#documentation--wiki)
+ - [Donations](#donations)
+ - [Translations](#translations)
+ - [Public Relations](#public-relations)
+
+
+
+
+---
+
+
+
+## Code of Conduct
This project and everyone participating in it is governed by the [KeeWeb Code of Conduct](https://github.com/keeweb/keeweb/blob/master/.github/CODE_OF_CONDUCT.md#readme).
By participating, you are expected to uphold this code. Please report unacceptable behavior to antelle.net@gmail.com.
-## Issues
+
-First, let's check if it's [already there](https://github.com/keeweb/keeweb/issues).
-Perhaps, someone has already reported it?
+
-[Click here](https://github.com/keeweb/keeweb/issues/new/choose) to create a new issue.
-When creating issues, please answer some questions asked on that page.
-They will help to understand, reproduce, and fix your issue.
+**[`^ back to top ^`](#contributing-to-keeweb)**
+
+
+
+
+
+---
+
+
+
+## Issues, Bugs, Ideas
+Stuff happens, and sometimes as best as we try, there may be issues with KeeWeb that we are unaware of. That is the great thing about open-source; anyone can use the program and contribute to making it better.
+
+
+
+If you have found a bug, have an issue with KeeWeb, or maybe even a cool idea; you can let us know by [submitting it](https://github.com/keeweb/keeweb/issues). However, before you submit your new issue, bug report, or feature request; head over to the [Issues Section](https://github.com/keeweb/keeweb/issues) and ensure nobody else has already submitted it.
+
+
+
+Once you are sure that your issue is not already being dealt with; you may submit it by clicking [here](https://github.com/keeweb/keeweb/issues/new/choose). You'll be asked to specify exactly what your new submission targets, such as:
+- Bug report
+- Feature Suggestion
+
+
+
+When submitting your new report, ensure you fill out any of the questions asked of you. If you do not provide enough information, we cannot help. Be as detailed as possible, and provide any logs or screenshots you may have to help us better understand what you mean. Failure to fill out the submission properly may result in it being closed without a response.
+
+
+
+If you are submitting a bug report:
+
+- Explain the issue in detail
+- Describe how you expect for a feature to work, and what you're seeing instead of what you expected.
+- Provide screenshots, logs, or anything else that can visually help track down the issue.
+
+
+
+If you have a generic question which isn't a bug or feature; you may want to submit it as a [Discussion](https://github.com/keeweb/keeweb/discussions) so that others in the community can respond.
+
+
+
+
+
+**[`^ back to top ^`](#contributing-to-keeweb)**
+
+
+
+
+
+---
+
+
## Vulnerabilities
-We would appreciate [responsible disclosure](https://en.wikipedia.org/wiki/Responsible_disclosure).
-If you would like to report a vulnerability, the preferred way to do so is [contacting the developer directly](mailto:antelle.net@gmail.com).
+If you believe that you have found a vulnerability, we would appreciate [responsible disclosure](https://en.wikipedia.org/wiki/Responsible_disclosure) from you. Since vulnerabilities can be sensitive, we ask that you email all reports to the following address:
-## Questions, great ideas, etc...
+
-You can [create an issue](https://github.com/keeweb/keeweb/issues/new/choose) to discuss any topic.
-Indeed, questions on that page are not applicable in this case.
+
+
+**[`^ back to top ^`](#contributing-to-keeweb)**
+
+
+
+
+
+---
+
+
## Development
+If you are looking to contribute to KeeWeb by actually submitting your own code; please review this section completely. There is important information and policies provided below that you must follow for your pull request to get accepted.
-We don't accept (and in foreseeable future, we won't accept) anyone as a project collaborator directly.
-Instead, the code should be contributed via pull requests. To get started with development, take a look at these pages:
+The source is here for everyone to collectively share and colaborate on. If you think you have a possible solution to a problem; don't be afraid to get your hands dirty.
+
+Unless you are fixing a known bug, we strongly recommend discussing it with the team by opening a [GitHub Discussion](https://github.com/keeweb/keeweb/discussions) you start in order to ensure your work does not conflict with future plans.
+
+All contributions are made via **Pull Requests**. To make a pull request, you will need a GitHub account; if you are unclear on this process, see GitHub's documentation on forking and pull requests.
+
+
+
+### Before Submitting Pull Requests
+
+- Follow the repository's code formatting conventions (see below);
+- Include tests that prove that the change works as intended and does not add regressions;
+- Document the changes in the code and/or the project's documentation;
+- Your PR must pass the CI pipeline;
+- When submitting your Pull Request, use one of the following branches:
+ - For bug fixes: `main` branch
+ - For features & functionality: `development` branch
+- Include a proper git commit message following the [Conventional Commit Specification](https://www.conventionalcommits.org/en/v1.0.0/#specification).
+
+
+
+If all of these items are checked, the pull request is ready to be reviewed and your pull request's label will be changed to "Ready for Review". At this point, a human will need to step in and manually verify your submission.
+
+Once your submission has been tested and verified; it will be merged.
+
+
+
+Before submitting your pull request, please review the following resources:
- [Architecture](https://github.com/keeweb/keeweb/wiki/Architecture)
- [Engineering](https://github.com/keeweb/keeweb/wiki/Engineering)
- [Unsupported Features](https://github.com/keeweb/keeweb/wiki/Unsupported%20Features)
- [Pull Request Guidelines](https://github.com/keeweb/keeweb/blob/master/.github/PULL_REQUEST_TEMPLATE.md#readme)
-## Pull requests
+
-Please follow [this guide](https://github.com/keeweb/keeweb/blob/master/.github/PULL_REQUEST_TEMPLATE.md#readme).
+### Conventional Commit Specification
-## Docs (Wiki pages)
+When commiting your changes, we require you to follow the Conventional Commit Specification, described below.
+
+**The Conventional Commits** is a specification for the format and content of a commit message. The concept behind Conventional Commits is to provide a rich commit history that can be read and understood by both humans and automated tools. Conventional Commits have the following format:
+
+
+
+```
+[(optional )]:
+
+[optional ]
+
+[optional