Merge pull request #38 from web3community/krishguptadev-patch-2

📝  docs: improve contributing file

Author: shuklaritvik06

CONTRIBUTING.md

@@ -1,13 +1,63 @@
-# Contributing guidelines ⚡️
+# Contributing Guidelines
 
-[![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square)](http://makeapullrequest.com) [![Open Source Love](https://badges.frapsoft.com/os/v1/open-source.png?v=103)](https://github.com/ellerbrock/open-source-badges/) [![License](https://img.shields.io/github/license/web3community/devprotocol.xyz)](https://github.com/web3community/devprotocol.xyz/blob/main/LICENSE)
+🎉 First of all, thanks for taking the time to contribute! 🎉
 
+The following is a set of guidelines for contributing to this project. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
 
-*👍🎉 First off, thanks for taking the time to contribute! 🎉👍*
+## Code of Conduct
 
+This project and everyone participating in it is governed by a [Code of Conduct](https://github.com/web3community/devprotcol.xyz/blob/main/code_of_conduct.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [@vinzvinci](https://github.com/vinzvinci)
 
-The following is a set of guidelines for contributing to this repository. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
+## How Can I Contribute?
 
+### Reporting Bugs
+
+This section guides you through submitting a bug report. Following these guidelines helps maintainers and the community understand your report 📝, reproduce the behavior 💻 💻, and find related reports 🔎.
+
+Since the new GitHub Issue forms we only suggest you to include most information possible. But you can also **Perform a [cursory search](https://github.com/web3community/devprotocol.xyz/issues)** to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
+
+> **Note:** If you find a **Closed** issue that seems like it is the same thing that you're experiencing, open a new issue and include a link to the original issue in the body of your new one.
+
+### Suggesting Enhancements
+
+This section guides you through submitting an enhancement suggestion, including completely new features and minor improvements to existing functionality. Following these guidelines helps maintainers and the community understand your suggestion 📝 and find related suggestions 🔎.
+
+Since the new GitHub Issue forms we only suggest you to include most information possible. But you can also **Perform a [cursory search](https://github.com/web3community/devprotocol.xyz/issues)** to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
+
+> **Note:** If you find a **Closed** issue that seems like it is the same thing that you're experiencing, open a new issue and include a link to the original issue in the body of your new one.
+
+### Your First Code Contribution
+
+Unsure where to begin contributing to this project? You can start by looking through these `beginner` and `help-wanted` issues:
+
+- [Beginner issues](https://github.com/web3community/devprotocol.xyz/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) - issues which should only require a few lines of code, and a test or two.
+- [Help wanted issues](https://github.com/web3community/devprotocol.xyz/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) - issues which should be a bit more involved than `beginner` issues.
+
+### Pull Requests
+
+The process described here has several goals:
+
+- Maintain the project's quality
+- Fix problems that are important to users
+- Engage the community in working toward the best possible!
+- Enable a sustainable system for maintainers to review contributions
+
+Please follow all instructions in [the template](https://github.com/web3community/devprotocol.xyz/blob/main/.github/pull_request_template.md)
+
+## Style Guide for Git Commit Messages :memo:
+
+**How you can add more value to your contribution logs:**
+
+- Use the present tense. (Example: "Add feature" instead of "Added feature")
+- Use the imperative mood. (Example: "Move item to...", instead of "Moves item to...")
+- Limit the first line (also called the Subject Line) to *50 characters or less*.
+- Capitalize the Subject Line.
+- Separate subject from body with a blank line.
+- Do not end the subject line with a period.
+- Wrap the body at *72 characters*.
+- Use the body to explain the *what*, *why*, *vs*, and *how*.
+- Reference [Issues](https://github.com/web3community/devprotocol.xyz/issues) and [Pull Requests](https://github.com/web3community/devprotocol.xyz/pulls) liberally after the first line.
+- Follow [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/)
 
 ## 🚀 How to Contribute
 
@@ -41,15 +91,15 @@ cd devprotocol.xyz
 git checkout -b your-branch-name
 ```
 
-**5.** Make the necessary changes in the source code.
+**5.** Make the necessary changes.
 
 **6.** Stage your changes and commit
 
 ```bash
 git add .
 git commit -m "<your_commit_message>"
 ```
-*You can use appropriate emojis for your commit messages from [Gitmoji](https://gitmoji.dev/)*
+*Follow our commit guide from above*
 
 **7.** Push your local commits to the remote repo.