resolved conflict in search-error

.gitignore

@@ -6,6 +6,7 @@
 .pnp.js
 .yarn/install-state.gz
 /package-lock.json
+/pnpm-lock.yaml
 
 # testing
 /coverage

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Openzone - GSSoC Contributors 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
+[Abhi Patel]https://www.linkedin.com/in/abhipatel001/
+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.

CONTRIBUTING.md

@@ -24,6 +24,40 @@ in case you are stuck:
 
 <br>
 
+### 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 repository yet, you can do so by clicking on the "File" menu and selecting "Clone Repository."
+   - Choose the 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 <branch-name>" 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.
+
+7. **Create a Pull Request:**
+  - Go to the GitHub website and navigate to your fork of the 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 repository.
+
 ## **Issue Report Process 📌**
 
 1. Go to the project's issues.

ISSUE_GUIDELINES.md

@@ -0,0 +1,42 @@
+## Issue Report Guidelines
+👍🎉 Thanks for taking the time to contribute! 🎉👍
+
+In order to give everyone a chance to submit a issues reports and contribute to the project, we have put restrictions in place. This section outlines the guidelines that should be imposed upon issue reports in the project.
+
+### Table of Contents
+ - Issue Management
+     - New Issues
+     - Existing Issues
+     - Feature Request Issues
+- General Guidelines
+
+
+- ### Issue Management
+ In all cases please use the GitHub open issue search to check whether the issue has already been reported.
+
+- ### New Issues
+To create new issues follow these steps:
+
+1). Your issue may have already been created. Search for duplicate open issues before submitting yours, for similar deficiencies in the code - duplicate issues are created.
+2). Verify whether the issue has been fixed by trying to reproduce it using the latest master or development branch in the repository.
+3). Click on the New Issue button
+4). Use the templates to create a standardized report of what needs to be done and why.
+5). If you want to be assigned the issue that you have created, then add a comment immediately after submitting it.
+We welcome contributors who find new ways to make the code better.
+
+- ### Existing Issues
+ You can also be a valuable contributor by searching for dormant issues. Here's how you can do that:
+
+ 1).Previously Assigned Issues: We regularly review issues and add a no-issue-activity label to them. Use the issue comments to ask whether the assignee is still working on the issue, and if not, ask for the issue to be assigned to you.
+ 2).Unassigned Issues: If the issue is already reported and not assigned to anyone and you are interested in working on the issue then:
+Ask for the issue to be assigned to you in the issue comments
+Ask our team to assign it to you on discord.
+ Working on these types of existing issues is a good way of getting started with the community.
+
+ - ### Feature Request Issues
+Feature requests are welcome. But take a moment to find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the mentors of the merits of this feature. Please provide as much detail and context as possible.
+
+ - ### General Guidelines
+Discuss issues in our various discord channels when necessary
+Please do not derail or troll issues.
+Keep the discussion on topic and respect the opinions of others.

README.md

@@ -1,28 +1,29 @@
-# OpenSource Project Explorer - Open Zone 
+# OpenSource Project Explorer - Open Zone🚀
 
+## About
 Welcome to the OpenZone! This platform aims to simplify the process of finding and contributing to open-source projects. Whether you're a seasoned contributor or just starting out, this platform will help you discover projects aligned with your interests and skills.
 
-## Features
+## ✨Features
 
-- **Project Search**: Easily search for open-source projects based on various criteria such as programming language, tags, and project activity.
-- **User Profile**: Maintain a comprehensive profile showcasing your contributions to open-source projects. Your profile will highlight the projects you've contributed to and your impact on them.
-- **Contribution Tracking**: Keep track of your contributions, including pull requests, commits, and issues opened or resolved.
+- **🔍Project Search**: Easily search for open-source projects based on various criteria such as programming language, tags, and project activity.
+- **👤User Profile**: Maintain a comprehensive profile showcasing your contributions to open-source projects. Your profile will highlight the projects you've contributed to and your impact on them.
+- **📈Contribution Tracking**: Keep track of your contributions, including pull requests, commits, and issues opened or resolved.
 
-## Technologies Used
+## 📈Technologies Used
 
-- **Next.js**: Next.js is a React framework that enables server-side rendering and easy React application development.
-- **TypeScript**: TypeScript adds static typing to JavaScript, providing better developer tooling and code quality.
-- **PNPM**: PNPM is a fast, disk-space-efficient package manager for Node.js projects.
+- **⚛️Next.js**: Next.js is a React framework that enables server-side rendering and easy React application development.
+- **🟦TypeScript**: TypeScript adds static typing to JavaScript, providing better developer tooling and code quality.
+- **📦PNPM**: PNPM is a fast, disk-space-efficient package manager for Node.js projects.
 
-## Getting Started
+## 🚀Getting Started
 
 Follow these steps to set up the project locally:
 
-### Prerequisites
+### ✅Prerequisites
 
-- Node.js and npm should be installed on your system.
+- `Node.js` and `npm` should be installed on your system.
 
-### Installation
+### 💾Installation
 
 1. Clone the repository:
 
@@ -42,7 +43,7 @@ Follow these steps to set up the project locally:
     pnpm install
     ```
 
-### Usage
+### ▶️Usage
 
 1. Start the development server:
 
@@ -52,7 +53,7 @@ Follow these steps to set up the project locally:
 
 2. Open your browser and visit `http://localhost:3000` to access the platform.
 
-## Contributing
+## 🤝Contributing
 
 We welcome contributions from the community! If you'd like to contribute to this project, please follow these steps:
 
@@ -64,10 +65,11 @@ We welcome contributions from the community! If you'd like to contribute to this
 
 Please ensure your code adheres to our coding standards and includes appropriate tests.
 
-## Contact
+## 📬Contact
 
 If you have any questions or suggestions, feel free to reach out to us at [![Linkedin Badge](https://img.shields.io/badge/-linkedIn-blue?style=flat&logo=Linkedin&logoColor=white)](https://www.linkedin.com/in/abhipatel001/)
 
 
----
+Thank you for contributing to OpenZone! Let's build something great together.
+#### Happy Coding!!
 

package.json

@@ -22,6 +22,7 @@
     "react": "^18",
     "react-dom": "^18",
     "react-icons": "^5.0.1",
+    "react-loading-skeleton": "^3.4.0",
     "tailwind-merge": "^2.2.2",
     "tailwindcss-animate": "^1.0.7"
   },