diff --git a/Contributing.md b/Contributing.md
index 10b29df..9c823df 100644
--- a/Contributing.md
+++ b/Contributing.md
@@ -1,31 +1,237 @@
+# Contributing To Collect Your GamingTools Repository ๐ฎ
+Thank you for your interest in contributing to **Collect Your GamingTools**! Weโre excited to see what creative ideas you bring. Follow these simple guidelines below to get started.
-# ๐ฎ Contributing to Collect Your GamingTools Repository
+
-Thank you for your interest in contributing to **Collect Your GamingTools**! Weโre excited to see what creative ideas you bring. Follow these simple guidelines below to get started.
+# Code of Conduct ๐
----
+Please read and follow our [Code of Conduct.](https://github.com/swaraj-das/Collect-your-GamingTools/blob/main/CODE_OF_CONDUCT.md)
-## ๐ Getting Started
+
-1. **Fork the Repository**
- Click the "Fork" button at the top-right corner to create your own copy of the repo.
+# Need Help With The Basics? ๐ค
-2. **Clone Your Fork**
- Clone your forked repository to your local machine:
- ```bash
- git clone https://github.com//Collect-your-GamingTools.git
- ```
+If you're new to Git and GitHub, no worries! Here are some useful resources:
-3. **Create a New Branch**
- Create a new branch for your changes:
- ```bash
- git checkout -b feature/your-feature-name
- ```
+- [Forking a Repository](https://help.github.com/en/github/getting-started-with-github/fork-a-repo)
+- [Cloning a Repository](https://help.github.com/en/desktop/contributing-to-projects/creating-an-issue-or-pull-request)
+- [How to Create a Pull Request](https://opensource.com/article/19/7/create-pull-request-github)
+- [Getting Started with Git and GitHub](https://towardsdatascience.com/getting-started-with-git-and-github-6fcd0f2d4ac6)
+- [Learn GitHub from Scratch](https://docs.github.com/en/get-started/start-your-journey/git-and-github-learning-resources)
+
+
+
+# Project Structure ๐
+
+```bash
+COLLECT-YOUR-GAMINGTOOLS/
+โโโ .github/ # GitHub-related configurations such as workflows, issue templates, etc
+โ
+โโโ backend/ # All the components of the project
+โ
+โโโ contributor/ # Contributor page in the project
+โ
+โโโ images/ # All the images in the project
+โ
+โโโ Loader/ # Loading paging for the project
+โ
+โโโ login/ # Login page in the project
+โ
+โโโ Policies/ # Privacy and other policies for the project
+โ
+โโโ popup/ # Pop Up action for the project
+โ
+โโโ SignUp/ # Sign Up page in the project
+โ
+โโโ .gitattributes/
+โ
+โโโ aboutus.html # About us page in the project
+โโโ
+โโโ CODE_OF_CONDUCT.md # Some rules for the contributors
+โโโ
+โโโ CONTRIBUTING.md # Instructions for the contributors
+โโโ
+โโโ darkMode.js
+โโโ
+โโโ docker-compose.yml
+โโโ
+โโโ Dockerfile
+โโโ
+โโโ index.html # Main page of the project
+โโโ
+โโโ LICENSE # A set of permissions to do something
+โโโ
+โโโ manifest.json
+โโโ
+โโโ pull_request_template.md
+โโโ
+โโโ README.md # Some instructions about the contribution
+โโโ
+โโโ script.js
+โโโ
+โโโ SECURITY.md
+โโโ
+โโโ service-worker.js
+โโโ
+โโโ style.css # Stylesheet document of the project
+โโโ
+```
+
+
+
+# Getting Started ๐
+
+1. **Star this repository**
+ Click on the top right corner marked as **Stars** at last.
+
+2. **Fork this repository**
+ Click on the top right corner marked as **Fork** at second last.
+
+3. **Clone the forked repository**
+
+```bash
+git clone https://github.com//Collect-your-GamingTools.git
+```
+
+4. **Navigate to the project directory**
+
+```bash
+cd Collect-your-GamingTools
+```
+
+5. **Create a new branch**
+
+```bash
+git checkout -b
+```
+
+6. **To make changes**
+
+```bash
+git add .
+```
+
+7. **Now to commit**
+
+```bash
+git commit -m "add comment according to your changes or addition of features inside this"
+```
+
+8. **Push your local commits to the remote repository**
+
+```bash
+git push -u origin
+```
+
+9. **Create a Pull Request**
+
+10. **Congratulations! ๐ you've made your contribution**
+
+
+
+# Alternatively, contribute using GitHub Desktop ๐ฅ๏ธ
+
+1. **Open GitHub Desktop:**
+ Launch GitHub Desktop and log in to your GitHub account if you haven't already.
+
+2. **Clone the Repository:**
+- If you haven't cloned the project repository yet, you can do so by clicking on the "File" menu and selecting "Clone Repository."
+- Choose the project repository from the list of repositories on GitHub and clone it to your local machine.
+
+3.**Switch to the Correct Branch:**
+- Ensure you are on the branch that you want to submit a pull request for.
+- If you need to switch branches, you can do so by clicking on the "Current Branch" dropdown menu and selecting the desired branch.
+
+4. **Make Changes:**
+- Make your changes to the code or files in the repository using your preferred code editor.
+
+5. **Commit Changes:**
+- In GitHub Desktop, you'll see a list of the files you've changed. Check the box next to each file you want to include in the commit.
+- Enter a summary and description for your changes in the "Summary" and "Description" fields, respectively. Click the "Commit to " button to commit your changes to the local branch.
----
+6. **Push Changes to GitHub:**
+- After committing your changes, click the "Push origin" button in the top right corner of GitHub Desktop to push your changes to your forked repository on GitHub.
-## ๐๏ธ Making Changes
+7. **Create a Pull Request:**
+- Go to the GitHub website and navigate to your fork of the project repository.
+- You should see a button to "Compare & pull request" between your fork and the original repository. Click on it.
+
+8. **Review and Submit:**
+- On the pull request page, review your changes and add any additional information, such as a title and description, that you want to include with your pull request.
+- Once you're satisfied, click the "Create pull request" button to submit your pull request.
+
+9. **Wait for Review:**
+Your pull request will now be available for review by the project maintainers. They may provide feedback or ask for changes before merging your pull request into the main branch of the project repository.
+
+
+
+# For Help And Support ๐ฌ
+
+- Admin Github Profile:- [SWARAJ DAS](https://github.com/swaraj-das)
+- Contact :- [Email](swarajdas625w@gmail.com)
+
+
+
+# Good Coding Practices ๐งโ๐ป
+
+1. **Follow the Project's Code Style**
+
+ - Maintain consistency with the existing code style (indentation, spacing, comments).
+ - Use meaningful and descriptive names for variables, functions, and classes.
+ - Keep functions short and focused on a single task.
+ - Avoid hardcoding values; instead, use constants or configuration files when possible.
+
+2. **Write Clear and Concise Comments**
+
+ - Use comments to explain why you did something, not just what you did.
+ - Avoid unnecessary comments that state the obvious.
+ - Document complex logic and functions with brief explanations to help others understand your thought -process.
+
+3. **Keep Code DRY (Don't Repeat Yourself)**
+
+ - Avoid duplicating code. Reuse functions, methods, and components whenever possible.
+ - If you find yourself copying and pasting code, consider creating a new function or component.
+
+4. **Write Tests**
+
+ - Write unit tests for your functions and components.
+ - Ensure your tests cover both expected outcomes and edge cases.
+ - Run tests locally before making a pull request to make sure your changes donโt introduce new bugs.
+
+5. **Code Reviews and Feedback**
+
+ - Be open to receiving constructive feedback from other contributors.
+ - Conduct code reviews for others and provide meaningful suggestions to improve the code.
+ - Always refactor your code based on feedback to meet the project's standards.
+
+
+
+# Pull Request Process ๐
+
+When submitting a pull request, please adhere to the following:
+
+1. **Self-review your code** before submission. ๐
+2. Include a detailed description of the functionality youโve added or modified.
+3. Comment your code, especially in complex sections, to aid understanding.
+4. Add relevant screenshots to assist in the review process.
+5. Submit your PR using the provided template and hang tight; we'll review it as soon as possible!
+
+
+
+# Issue Report Process ๐
+
+To report an issue, follow these steps:
+
+1. Navigate to the project's issues section :- [Issues](https://github.com/swaraj-das/Collect-your-GamingTools/issues/new/choose)
+2. Please kindly choose the appropriate template according to your issue.
+3. Provide a clear and concise description of the issue.
+4. Wait until someone looks into your report.
+5. Begin working on the issue only after you have been assigned to it. ๐
+
+
+
+# Making Changes ๐๏ธ
1. **Code Changes**
Make your modifications, ensuring they align with the projectโs coding standards and code of conduct. Add exciting features, enriching documentation or squash bugs!
@@ -42,19 +248,19 @@ Thank you for your interest in contributing to **Collect Your GamingTools**! We
git push origin feature/your-feature-name
```
----
+
+
+# Additional Notes ๐
-## ๐ ๏ธ Creating a Pull Request
+- Make sure to sync your fork with the latest changes from the original repo before pushing new features.
+- Respect coding conventions and keep your code clean. Comment your changes for ease in review.
-1. Once your changes are pushed, create a pull request (PR) on the original repository.
-2. Provide a detailed description of your changes and link any relevant issues. Provide relevant images/videos, if any.
-3. Wait for reviews and engage with feedback!
+Welcome to Open-Source and thank you for contributing! ๐
----
+
-## ๐ Additional Notes
+# Thank you for contributing ๐
-- Make sure to sync your fork with the latest changes from the original repo before pushing new features.
-- Respect coding conventions and keep your code clean. Comment your changes for ease in review.
+We truly appreciate your time and effort to help improve our project. Feel free to reach out if you have any questions or need guidance. Happy coding! ๐
-Welcome to Open-Source and thank you for contributing! ๐
\ No newline at end of file
+##
\ No newline at end of file