From e7cfd6ea212e0307d5018940674f13be0523efd5 Mon Sep 17 00:00:00 2001 From: Manish Bisht <89926834+ManishBisht777@users.noreply.github.com> Date: Sun, 1 Oct 2023 18:27:19 +0530 Subject: [PATCH 1/5] docs: CODE_OF_CONDUCT --- CODE_OF_CONDUCT.md | 128 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 128 insertions(+) create mode 100644 CODE_OF_CONDUCT.md diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..18c9147 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,128 @@ +# Contributor Covenant Code of Conduct + +## Our Pledge + +We as members, contributors, and leaders pledge to make participation in our +community a harassment-free experience for everyone, regardless of age, body +size, visible or invisible disability, ethnicity, sex characteristics, gender +identity and expression, level of experience, education, socio-economic status, +nationality, personal appearance, race, religion, or sexual identity +and orientation. + +We pledge to act and interact in ways that contribute to an open, welcoming, +diverse, inclusive, and healthy community. + +## Our Standards + +Examples of behavior that contributes to a positive environment for our +community include: + +* Demonstrating empathy and kindness toward other people +* Being respectful of differing opinions, viewpoints, and experiences +* Giving and gracefully accepting constructive feedback +* Accepting responsibility and apologizing to those affected by our mistakes, + and learning from the experience +* Focusing on what is best not just for us as individuals, but for the + overall community + +Examples of unacceptable behavior include: + +* The use of sexualized language or imagery, and sexual attention or + advances of any kind +* Trolling, insulting or derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or email + address, without their explicit permission +* Other conduct which could reasonably be considered inappropriate in a + professional setting + +## Enforcement Responsibilities + +Community leaders are responsible for clarifying and enforcing our standards of +acceptable behavior and will take appropriate and fair corrective action in +response to any behavior that they deem inappropriate, threatening, offensive, +or harmful. + +Community leaders 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, and will communicate reasons for moderation +decisions when appropriate. + +## Scope + +This Code of Conduct applies within all community spaces, and also applies when +an individual is officially representing the community in public spaces. +Examples of representing our community include using an official e-mail address, +posting via an official social media account, or acting as an appointed +representative at an online or offline event. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported to the community leaders responsible for enforcement at +. +All complaints will be reviewed and investigated promptly and fairly. + +All community leaders are obligated to respect the privacy and security of the +reporter of any incident. + +## Enforcement Guidelines + +Community leaders will follow these Community Impact Guidelines in determining +the consequences for any action they deem in violation of this Code of Conduct: + +### 1. Correction + +**Community Impact**: Use of inappropriate language or other behavior deemed +unprofessional or unwelcome in the community. + +**Consequence**: A private, written warning from community leaders, providing +clarity around the nature of the violation and an explanation of why the +behavior was inappropriate. A public apology may be requested. + +### 2. Warning + +**Community Impact**: A violation through a single incident or series +of actions. + +**Consequence**: A warning with consequences for continued behavior. No +interaction with the people involved, including unsolicited interaction with +those enforcing the Code of Conduct, for a specified period of time. This +includes avoiding interactions in community spaces as well as external channels +like social media. Violating these terms may lead to a temporary or +permanent ban. + +### 3. Temporary Ban + +**Community Impact**: A serious violation of community standards, including +sustained inappropriate behavior. + +**Consequence**: A temporary ban from any sort of interaction or public +communication with the community for a specified period of time. No public or +private interaction with the people involved, including unsolicited interaction +with those enforcing the Code of Conduct, is allowed during this period. +Violating these terms may lead to a permanent ban. + +### 4. Permanent Ban + +**Community Impact**: Demonstrating a pattern of violation of community +standards, including sustained inappropriate behavior, harassment of an +individual, or aggression toward or disparagement of classes of individuals. + +**Consequence**: A permanent ban from any sort of public interaction within +the community. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], +version 2.0, available at +https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. + +Community Impact Guidelines were inspired by [Mozilla's code of conduct +enforcement ladder](https://github.com/mozilla/diversity). + +[homepage]: https://www.contributor-covenant.org + +For answers to common questions about this code of conduct, see the FAQ at +https://www.contributor-covenant.org/faq. Translations are available at +https://www.contributor-covenant.org/translations. From d796b637c81d2355aba7a12edb5e37e14fe504a6 Mon Sep 17 00:00:00 2001 From: Manish Bisht <89926834+ManishBisht777@users.noreply.github.com> Date: Sun, 1 Oct 2023 18:31:55 +0530 Subject: [PATCH 2/5] docs: CONTRIBUTING.md --- CONTRIBUTING.md | 44 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 CONTRIBUTING.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..33b2dad --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,44 @@ +# Contributing Guide + +## Issues & Pull Requests + +### Creating an Issue + +Before **creating** an Issue for `features`/`bugs`/`improvements` please follow these steps: + +1. search existing Issues before creating a new issue (has someone raised this already) +1. if it doesn't exist create a new issue giving as much context as possible (please select the correct Issue type, for example `bug` or `feature`) + +### Working on an Issue (get it assigned to you) + +Before working on an existing Issue please follow these steps: + +1. only ask to be assigned 1 issue at a time +1. comment asking for the issue to be assigned to you (do not tag maintainers on GitHub or Discord as all maintainers receive your comment notifications) +1. after the Issue is assigned to you, you can start working on it +1. **only** start working on this Issue (and open a Pull Request) when it has been assigned to you - this will prevent confusion, multiple people working on the same issue and work not being used +1. do **not** enable GitHub Actions on your fork +1. reference the Issue in your Pull Request (for example `closes #123`) + +> Notes: +> - check the `Assignees` box at the top of the page to see if the issue has been assigned to someone else before requesting this be assigned to you +> - if an Issue is unclear, ask questions to get more clarity before asking to have the Issue assigned to you +> - only request to be assigned an Issue if you know how to work on it +> - an Issue can be assigned to multiple people, if you all agree to collaborate on the issue (the Pull Request can contain commits from different collaborators) +> - any Issues that have no activity after 2 weeks will be unassigned and re-assigned to someone else + +## Reviewing Pull Requests + +We welcome everyone to review Pull Requests, it is a great way to learn, network and support each other. + +### DOs + +- be kind and respectful, we use inclusive, gender neutral language (for example `they/them` instead of `guy/man`) +- use inline comments to explain your suggestions +- use inline suggestions to propose changes + +### DON'Ts + +- do not be rude, disrespectful or aggressive +- do not repeat feedback, this creates more noise than value (check the existing conversation), use GitHub reactions if you agree/disagree with a comment +- do not blindly approve pull requests to improve your GitHub contributors graph From 0e8441b8bb723ace8d3d015ceb90eef22aacfc47 Mon Sep 17 00:00:00 2001 From: Manish Bisht <89926834+ManishBisht777@users.noreply.github.com> Date: Sun, 1 Oct 2023 18:32:40 +0530 Subject: [PATCH 3/5] docs: LICENSE --- LICENSE | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 LICENSE diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..ab2e5e0 --- /dev/null +++ b/LICENSE @@ -0,0 +1,21 @@ +MIT License + +Copyright (c) 2023 Frontend Freaks + +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. From a5f01236d7a3a4e10048fa7734fa70a4ad30505b Mon Sep 17 00:00:00 2001 From: sarveshpyadav <8sarveshyadav@gmail.com> Date: Mon, 2 Oct 2023 12:02:59 +0530 Subject: [PATCH 4/5] Fix nav bar for mobile and desktop --- components/layout/main-nav.tsx | 4 ++-- components/layout/mobile-nav.tsx | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/components/layout/main-nav.tsx b/components/layout/main-nav.tsx index 6d926b2..25182e4 100644 --- a/components/layout/main-nav.tsx +++ b/components/layout/main-nav.tsx @@ -48,8 +48,8 @@ export default function MainNav({ items, children }: MainNavProps) { className="flex items-center space-x-2 md:hidden" onClick={() => setShowMobileMenu(!showMobileMenu)} > - {showMobileMenu ? : } - Menu + {/* {showMobileMenu ? : } */} + Frontend Freaks {showMobileMenu && items && ( {children} diff --git a/components/layout/mobile-nav.tsx b/components/layout/mobile-nav.tsx index d427db0..5b42fe0 100644 --- a/components/layout/mobile-nav.tsx +++ b/components/layout/mobile-nav.tsx @@ -19,7 +19,7 @@ export function MobileNav({ items, children }: MobileNavProps) {
- Frontend + Menu