UMatter

Check the Website here. Welcome to UMatter, an inclusive platform designed to help individuals quit bad habits by providing personalized sessions and one-on-one consultations with professionals.

UMatter is an one and all platform to help people quitting bad habits by providing them personalized sessions and one to one consultations with professionals.

Tech Stack Used

𝗛𝗧𝗠𝗟5	𝗖𝗦𝗦3	𝗕𝗢𝗢𝗦𝗧𝗥𝗔𝗣	𝗝𝗔𝗩𝗔𝗦𝗖𝗥𝗜𝗣𝗧	REACTJS

Website Overview

UMatter is committed to supporting individuals on their journey to overcome bad habits. Our website offers a range of services and resources to help users make positive changes in their lives. With a user-friendly interface and a team of dedicated professionals, UMatter is here to guide and empower you every step of the way.

Key Features ✨

• Landing Page: When you visit our website, you'll be greeted by an engaging landing page that captures the essence of UMatter. Get inspired to take the first step towards a healthier and happier life.

• About Us: Learn more about UMatter and our mission. Discover how our platform can provide you with the necessary tools and support to break free from bad habits.

Components of Website

Landing Page

This page appears when user clicks on the site and lands on the page.

About Us

This Page gives user the brief about the website and what they can expect.

Services Page

This page provides the list of services which ae available on our website.

🔖Steps to Contribute ✅

Following are the steps to guide you:

• Step 1: Fork the repo and Go to your Git terminal and clone it on your machine.

  git clone https://github.com/<your_github_username>/UMatter.git
  

• Step 2: Add an upstream link to the main branch in your cloned repo

  git remote add upstream https://github.com/MonalikaPatnaik/UMatter.git
  

• Step 3: Keep your cloned repo up to date by pulling from upstream (this will also avoid any merge conflicts while committing new changes)

  git pull upstream main
  

• Step 4: Create your feature branch (This is a necessary step, so don't skip it)

  git checkout -b <feature-name>
  

• Step 5: Track and stage your changes.

   # Track the changes
   git status
  
   # Add changes to Index
   git add .
  

• Step 6: Commit all the changes (Write commit message as "Small Message")

  git commit -m "Write a meaningful but small commit message"
  

• Step 7: Push the changes for review

  git push origin <branch-name>
  

• Step 8: Create a PR on Github. (Don't just hit the create a pull request button, you must write a PR message to clarify why and what are you contributing)

✨🔨Note:

• Do not edit/delete someone else's script in this repository. You can only insert new files/folders into this repository.

• Give a meaningful name to whatever file or folder you are adding.

🔑Guidelines✨

1. Welcome to this repository, if you are here as an open-source program participant/contributor.
2. Participants/contributors have to comment on issues they would like to work on, and mentors or the PA will assign you.
3. Issues will be assigned on a first-come, first-serve basis.
4. Participants/contributors can also open their issues using issue_template, but it needs to be verified and labelled by a mentor or PA. Please discuss with the team once before opening your issues. We respect all your contributions, whether it is an Issue or a Pull Request.
5. When you raise an issue, make sure you get it assigned to you before you start working on that project.
6. Each participant/contributor will be assigned 1 issue (max) at a time to work.
7. Participants are expected to follow project guidelines and coding style . Structured code is one of our top priorities.
8. Try to explain your approach to solve any issue in the comments. This will increase the chances of you being assigned.
9. Don't create issues that are already listed.
10. Please don't pick up an issue already assigned to someone else. Work on the issues after it gets assigned to you.
11. Make sure you discuss issues before working on the issue.
12. Pull requests will be merged after being reviewed by a mentor or PA.
13. It might take a day or two to review your pull request. Please have patience and be nice.
14. Always create a pull request from a branch other than main.
15. Participants/contributors have to complete issues before the decided Deadline. If you fail to make a PR within the deadline, then the issue will be assigned to another person in the queue.
16. While making PRs, don't forget to add a description of your work.
17. Include issue number (Fixes: issue number) in your commit message while creating a pull request.
18. Make sure your solution to any issue is better in terms of performance and other parameters in comparison to the previous work.
19. We all are here to learn. You are allowed to make mistakes. That's how you learn, right!.

😎 Project Maintainers

Monalika Patnaik

Sneha Chauhan

Mansi

License 🪪

UMatter is released under the MIT license. See the LICENSE file for more details

😃 Happy Contributing 😃