Initial commit

Author: shadil-rayyan

.dockerignore

@@ -0,0 +1,7 @@
+node_modules
+npm-debug.log
+Dockerfile
+.dockerignore
+.git
+.gitignore
+.next/cache

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# Universal CODEOWNERS file
+shadilrayyan2@gmail.com

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,133 @@
+
+# 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, caste, color, 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 email 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
+[INSERT CONTACT METHOD].
+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.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

.github/CONTRIBUTING.md

@@ -0,0 +1,107 @@
+# Contributing to the Project
+
+Thank you for your interest in contributing to this Next.js open-source project! We welcome contributions of all kinds, including bug fixes, new features, documentation improvements, and more. Please read the following guidelines to ensure a smooth and collaborative contribution process.
+
+## 📌 Getting Started
+
+### 🔹 Fork and Clone the Repository
+1. **Fork** the repository on GitHub.
+2. **Clone** your fork to your local machine:
+   ```sh
+   git clone https://github.com/your-username/your-project.git
+   ```
+3. Navigate into the project directory:
+   ```sh
+   cd your-project
+   ```
+4. Add the upstream repository:
+   ```sh
+   git remote add upstream https://github.com/original-author/your-project.git
+   ```
+5. Ensure your fork is up to date with the upstream repository:
+   ```sh
+   git pull upstream main
+   ```
+
+### 🔹 Install Dependencies
+Ensure you have **Node.js (LTS)** and **npm** or **yarn** installed, then install project dependencies:
+   ```sh
+   npm install
+   # or
+   yarn install
+   ```
+
+### 🔹 Running the Project Locally
+Start the development server:
+   ```sh
+   npm run dev
+   # or
+   yarn dev
+   ```
+Visit `http://localhost:3000` to see the project running.
+
+## 🚀 Contribution Workflow
+
+### 🔹 Reporting Issues
+Before opening an issue, check the [existing issues](https://github.com/original-author/your-project/issues) to avoid duplicates. 
+If you find a bug, experience a performance issue, or have a feature request:
+1. Open a **new issue** with a clear and concise description.
+2. Provide **steps to reproduce** the issue if applicable.
+3. Suggest possible fixes or improvements if you have any ideas.
+
+### 🔹 Submitting Pull Requests (PRs)
+1. **Create a new branch** from `main`:
+   ```sh
+   git checkout -b feature/your-feature
+   ```
+2. Implement your changes following the project’s coding standards.
+3. **Run tests** to ensure everything is working correctly:
+   ```sh
+   npm run test
+   ```
+4. **Commit your changes** with a meaningful commit message:
+   ```sh
+   git commit -m "feat: add new feature"
+   ```
+5. **Push your branch** to GitHub:
+   ```sh
+   git push origin feature/your-feature
+   ```
+6. **Open a Pull Request (PR)** and provide a clear description of your changes.
+7. Address any feedback from maintainers and update your PR if necessary.
+
+## 📏 Code Guidelines
+
+### 🔹 Code Style
+- Follow **Next.js best practices**.
+- Write **clean, modular, and maintainable code**.
+- Use **ESLint and Prettier** to ensure consistent formatting:
+  ```sh
+  npm run lint
+  ```
+
+### 🔹 Commit Message Convention
+Use [Conventional Commits](https://www.conventionalcommits.org/):
+```
+type(scope): message
+```
+Examples:
+- `feat(auth): add login functionality`
+- `fix(ui): resolve navbar bug`
+
+### 🔹 Branch Naming Convention
+Follow a structured naming convention for branches:
+- **Features:** `feature/your-feature-name`
+- **Bug Fixes:** `fix/your-bug-fix`
+- **Documentation Updates:** `docs/update-docs`
+
+## 🤝 Community Guidelines
+- Be **respectful** and **inclusive**.
+- Keep discussions **constructive** and **helpful**.
+- Follow the [Code of Conduct](CODE_OF_CONDUCT.md) (if applicable).
+
+## 💡 Need Help?
+Join the discussions in GitHub issues or reach out to the maintainers. 
+
+We appreciate your contributions! 🚀
+

.github/ISSUE_TEMPLATE/bug-report.yaml

@@ -0,0 +1,100 @@
+name: Bug Report
+
+description: Report an issue encountered while using the software.
+
+labels: 
+  - kind/bug
+
+body:
+  - type: textarea
+    id: problem
+    attributes:
+      label: What happened?
+      description: |
+        Describe the issue you encountered in detail. Providing clear and concise information helps in addressing the issue faster.
+        If this is a security-related issue, please disclose it privately via the appropriate security channels (if applicable).
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: What did you expect to happen?
+      description: Explain the behavior you expected from the software.
+    validations:
+      required: true
+
+  - type: textarea
+    id: repro
+    attributes:
+      label: Steps to Reproduce
+      description: Provide the steps to reproduce the issue as minimally and precisely as possible.
+    validations:
+      required: true
+
+  - type: textarea
+    id: softwareVersion
+    attributes:
+      label: Software Version
+      description: |
+        Specify the version of the software where you encountered this issue. If applicable, provide details on the branch, build, or release version.
+
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment Details
+      description: |
+        Provide details about the environment where this issue occurred. This could include operating system, platform, cloud provider, or any other relevant context.
+      value: |
+        <details>
+        
+        ```console
+        # On Linux/MacOS:
+        $ uname -a
+        $ cat /etc/os-release
+        # paste output here
+        
+        # On Windows:
+        C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
+        # paste output here
+        ```
+        
+        </details>
+
+  - type: textarea
+    id: installTools
+    attributes:
+      label: Installation Method
+      description: Specify the installation tools or package managers used (if applicable).
+
+  - type: textarea
+    id: dependencies
+    attributes:
+      label: Related Dependencies or Plugins
+      description: |
+        List any plugins, modules, or dependencies (and their versions) that might relate to this issue.
+      value: |
+        <details>
+        
+        </details>
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs, Errors, or Debugging Output
+      description: |
+        Provide any relevant logs, stack traces, or debugging output that can help diagnose the issue.
+      value: |
+        <details>
+        
+        ```console
+        # Paste logs or errors here.
+        ```
+        
+        </details>
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional Context
+      description: Include any other details that might help diagnose the issue.

.github/ISSUE_TEMPLATE/config.yaml

@@ -0,0 +1,3 @@
+contact_links:
+  - name: Support Request
+    url: shadilrayyan2@gmail.com