Skip to content

Commit

Permalink
Adding Responsiveness & Hover Effect.
Browse files Browse the repository at this point in the history 
I have added the responsiveness to the web pages and also the hover effect to the various cards .
  • Loading branch information
@Mohit5Upadhyay
Mohit5Upadhyay authored May 10, 2024
1 parent cb2c2a0 commit 76592de
Show file tree
Hide file tree
Showing 12 changed files with 1,548 additions and 263 deletions.
82 changes: 41 additions & 41 deletions CODE_OF_CONDUCT.md
View file
Original file line number Diff line number Diff line change
@@ -1,41 +1,41 @@
# Code of Conduct

## Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

## Our Standards

Examples of behavior that contributes to creating a positive environment include:

- Using welcoming and inclusive language
- Being respectful of differing viewpoints and experiences
- Gracefully accepting constructive criticism
- Focusing on what is best for the community
- Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

- The use of sexualized language or imagery and unwelcome sexual attention or advances
- Trolling, insulting/derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information, such as a physical or electronic address, without explicit permission
- Other conduct which could reasonably be considered inappropriate in a professional setting

## Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

## Scope

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.


## Attribution

This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html), version 2.0, available at [https://www.contributor-covenant.org/version/2/0/code_of_conduct.html](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html).

For answers to common questions about this code of conduct, see [FAQ](https://www.contributor-covenant.org/faq).

# Code of Conduct

## Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

## Our Standards

Examples of behavior that contributes to creating a positive environment include:

- Using welcoming and inclusive language
- Being respectful of differing viewpoints and experiences
- Gracefully accepting constructive criticism
- Focusing on what is best for the community
- Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

- The use of sexualized language or imagery and unwelcome sexual attention or advances
- Trolling, insulting/derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information, such as a physical or electronic address, without explicit permission
- Other conduct which could reasonably be considered inappropriate in a professional setting

## Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

## Scope

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.


## Attribution

This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html), version 2.0, available at [https://www.contributor-covenant.org/version/2/0/code_of_conduct.html](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html).

For answers to common questions about this code of conduct, see [FAQ](https://www.contributor-covenant.org/faq).

42 changes: 21 additions & 21 deletions LICENSE
View file
Original file line number Diff line number Diff line change
@@ -1,21 +1,21 @@
MIT License

Copyright (c) 2024 Khushi Joshi

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
MIT License
Copyright (c) 2024 Khushi Joshi
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
132 changes: 66 additions & 66 deletions Learn.md
View file
Original file line number Diff line number Diff line change
@@ -1,66 +1,66 @@



# Contributing to Foodie - A Food Ordering Website

Welcome to Foodie's open-source project! We're thrilled that you're interested in contributing. This guide will help you get started with making your first contribution to the project.

## How to Contribute

1. **Fork the Repository**: Click the "Fork" button in the top-right corner of this repository's page to create your own copy of the project.

2. **Clone Your Fork**: Clone the repository to your local machine using the following command:
```bash
git clone https://github.com/yourusername/FoodOrderingWebsite.git
```

3. **Navigate to the Project Directory**: Enter the directory of the cloned project:
```bash
cd FoodOrderingWebsite
```

4. **Set Up Remote Upstream**: Connect your fork to the original repository to stay updated with its changes:
```bash
git remote add upstream https://github.com/originalusername/FoodOrderingWebsite.git
```

5. **Create a Branch**: Before making any changes, create a new branch to work on your feature or bug fix:
```bash
git checkout -b feature-or-fix-name
```

6. **Make Changes**: Now you're ready to make your changes! Feel free to modify existing code, add new features, or fix bugs.

7. **Commit Your Changes**: Once you've made your changes, commit them with a descriptive message:
```bash
git add .
git commit -m "Add feature or fix"
```

8. **Push Changes to Your Fork**: Push your changes to your fork on GitHub:
```bash
git push origin feature-or-fix-name
```

9. **Submit a Pull Request**: Go to your fork on GitHub and click on the "New Pull Request" button. Provide a descriptive title and detailed description of your changes. Then, submit the pull request for review.

## Code Guidelines

- Follow the existing code style and structure.
- Write clear and concise commit messages.
- Test your changes thoroughly before submitting a pull request.

## Resources

- [GitHub Forking Guide](https://docs.github.com/en/get-started/quickstart/fork-a-repo)
- [Git Handbook](https://guides.github.com/introduction/git-handbook/)
- [Markdown Cheat Sheet](https://www.markdownguide.org/cheat-sheet/)

## Contact

If you have any questions or need assistance, feel free to reach out to us via [GitHub Issues](https://github.com/yourusername/FoodOrderingWebsite/issues).

We appreciate your contributions!
```
You can copy and paste this content into a `learn.md` file in your repository. Let me know if you need further assistance!



# Contributing to Foodie - A Food Ordering Website

Welcome to Foodie's open-source project! We're thrilled that you're interested in contributing. This guide will help you get started with making your first contribution to the project.

## How to Contribute

1. **Fork the Repository**: Click the "Fork" button in the top-right corner of this repository's page to create your own copy of the project.

2. **Clone Your Fork**: Clone the repository to your local machine using the following command:
```bash
git clone https://github.com/yourusername/FoodOrderingWebsite.git
```

3. **Navigate to the Project Directory**: Enter the directory of the cloned project:
```bash
cd FoodOrderingWebsite
```

4. **Set Up Remote Upstream**: Connect your fork to the original repository to stay updated with its changes:
```bash
git remote add upstream https://github.com/originalusername/FoodOrderingWebsite.git
```

5. **Create a Branch**: Before making any changes, create a new branch to work on your feature or bug fix:
```bash
git checkout -b feature-or-fix-name
```

6. **Make Changes**: Now you're ready to make your changes! Feel free to modify existing code, add new features, or fix bugs.

7. **Commit Your Changes**: Once you've made your changes, commit them with a descriptive message:
```bash
git add .
git commit -m "Add feature or fix"
```

8. **Push Changes to Your Fork**: Push your changes to your fork on GitHub:
```bash
git push origin feature-or-fix-name
```

9. **Submit a Pull Request**: Go to your fork on GitHub and click on the "New Pull Request" button. Provide a descriptive title and detailed description of your changes. Then, submit the pull request for review.

## Code Guidelines

- Follow the existing code style and structure.
- Write clear and concise commit messages.
- Test your changes thoroughly before submitting a pull request.

## Resources

- [GitHub Forking Guide](https://docs.github.com/en/get-started/quickstart/fork-a-repo)
- [Git Handbook](https://guides.github.com/introduction/git-handbook/)
- [Markdown Cheat Sheet](https://www.markdownguide.org/cheat-sheet/)

## Contact

If you have any questions or need assistance, feel free to reach out to us via [GitHub Issues](https://github.com/yourusername/FoodOrderingWebsite/issues).

We appreciate your contributions!
```
You can copy and paste this content into a `learn.md` file in your repository. Let me know if you need further assistance!
Loading

0 comments on commit 76592de

Please sign in to comment.