abidsyed25/scrapquest

ScrapQuest is your go-to solution for effortlessly extracting data from websites. It's a powerful web scraper built with Next.js, TypeScript, and Puppeteer with Browserless. With ScrapQuest, you can quickly gather valuable information from any website without hassle.

ScrapQuest

---

⚡About Us:

ScrapQuest is your go-to solution for effortlessly extracting data from websites. It's a simple yet powerful web scraper built with Next.js, TypeScript, and Puppeteer with Browserless. With ScrapQuest, you can quickly gather valuable information from any website without hassle.

---

⚡short video for reference:

ScrapQuest.mp4

Frontend Deployed here :- scrap-quest.vercel.app/

Note

Due to some limitations, website functionality is limited on vercel. So setup project locally for complete functionality

---

Tech Stack

• Next.js: A React framework for building server-side rendered and static web applications.
• Puppeteer: A Node.js library for controlling headless Chrome or Chromium, used here for web scraping.
• Browserless: A service that provides headless browser instances for Puppeteer.
• TypeScript: A statically typed superset of JavaScript that adds type definitions for improved code quality and developer productivity.

---

⚡Setup locally

Follow these steps to set up ScrapQuest locally:

Prerequisites

• Node.js (version 18) installed on your machine. You can download it here.

Steps

Using Docker

1. Fork the Repository

2. Clone your Fork from GitHub
   

   git clone https://github.com/<your-user-name>/ScrapQuest.git

3. cd ScrapQuest

4. docker-compose up

- open localhost:3000 on the browser

Without Docker

1. Fork the Repository

2. Clone your Fork from GitHub
   

   git clone https://github.com/<your-user-name>/ScrapQuest.git

3. cd ScrapQuest

4. npm install

5. npm run dev

• open localhost:3000 on the browser

✍️ Open Source Contribution Welcome:

We welcome contributions from the community to improve ScrapQuest. Whether it's bug fixes, feature enhancements, or documentation improvements, your contributions are valuable.

---

✨Contribution Guidelines:

To submit your contributions, follow these steps:

1. Fork the Repository: Click the "Fork" button at the top right corner of the repository to create your own copy.

2. Clone Your Fork: Clone your forked repository to your local machine using the following command:

   git clone https://github.com/Your-Username/ScrapQuest.git
   

3. Create a Branch: Create a new branch for your changes:

   git checkout -b my-feature
   

4. Make Changes: Make your desired changes to the codebase.

5. Commit Changes: Commit your changes with a descriptive commit message:

   git commit -m "Add new feature"
   

6. Push Changes: Push your changes to your forked repository:

   git push origin my-feature
   

7. Submit a Pull Request: Go to your forked repository on GitHub and submit a pull request. Be sure to provide a detailed description of your changes and why they are necessary.

---

Code of Conduct:

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms. And we appreciate your interest in contributing to ScrapQuest! Let's make it better together.

---

⚡ Featured In:

Open Source Programs

Event Logo	Event Name	Event Description
	GirlScript Summer of Code 2024	GirlScript Summer of Code is a three-month-long Open Source Program conducted every summer by GirlScript Foundation. It is an initiative to bring more beginners to Open-Source Software Development.

---

License:

This project is licensed under the MIT License.

---

Our Contributors ❤️

Thank you for contributing to our repository

We appreciate your help in making ScrapQuest even better.😃

Support

Don't forget to leave a star for this project!

Go to Top

---

Made with ❤️ by Abid

scrapquest's Issues

Update readme file

In the readme file, contribution guidelines link is not working. When clicked on contribution guidelines it should navigate to the code of conduct file.
Also make changes in the first two steps to set project locally.

1. git clone https://github.com/Abidsyed25/scrapquest.git
2. cd scrapquest

💡[FEATURE]: Add an About Us Page

Is your feature request related to a problem? Please describe.
Users often express frustration when they cannot easily find information about our company, our mission, and the team behind our products. This lack of transparency can lead to mistrust or a sense of detachment from our brand. An About Page is crucial for providing this information in a clear and accessible manner.

Describe the solution you'd like
We propose the addition of an About Page to our website.

Please assign me this issue as part of GSSoC'24 @Abidsyed25 . Thank you!

🪲[Bug]: Web app responsiveness on small screen devices

Describe the bug

The web app fails to display correctly on small screen devices. Elements overlap, and the layout is distorted, hindering navigation and usability.

To Reproduce

Steps to reproduce the behavior:

1. Open the web app on a small screen device (e.g., smartphone or tablet).
2. Navigate to the main page or any significant page.
3. Scroll through the page and observe the layout and element alignment.
4. Note the overlapping elements and distorted layout.

Expected behavior

The web app should adapt its layout for small screens, ensuring all elements are properly aligned without overlap, and maintaining smooth, user-friendly navigation.

Screenshots

Desktop (please complete the following information):

• OS: [e.g., Windows 10]
• Browser: [e.g., Chrome]
• Version: [e.g., 90.0]

Smartphone (please complete the following information):

• Device: [e.g., iPhone 12]
• OS: [e.g., iOS 14.4]
• Browser: [e.g., Safari]
• Version: [e.g., 14]

Additional context

This issue significantly impacts the user experience on mobile devices, making it crucial to resolve for better accessibility and usability across all device types.

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSOC'24 contributor
• I want to work on this issue

Home_Page UI

Home_page UI

Need improvements on the UI
-A Proper Landing Page
-Footer
-I will work on this issue .Please assign this to me under GSSOC24.
-Please mention the level

📝[Docs]: Pull Request Template Creation

What Docs changes are you proposing?
Provide a clear description of the changes you're proposing for the documentation. Are you suggesting corrections, clarifications, additions, or updates?
I am writing to express my interest in contributing to your repository by creating a pull request template.
I believe that having a standardized template will help streamline the contribution process, ensuring that all necessary information is included and making it easier for maintainers to review and merge pull requests.
Could you please assign me the issue under gssoc24? I am excited about the opportunity to contribute to your project and help improve the workflow for all contributors.

Why do the Docs need this improvement? What is the motivation for this change? How will this change benefit the community?
Explain the motivation behind the proposed changes and how they will benefit the community or users of the documentation.

Describe the solution you'd like
Provide a clear and concise description of the changes you'd like to see implemented in the documentation.

Describe alternatives you've considered
If you've thought about alternative approaches or solutions, briefly describe them here.

Additional context
Add any additional context, examples, or screenshots related to the proposed documentation changes.

💡[FEATURE]: Add About us Page

I would like to add the about us page so that user can know what actually we do .

There in the navbar i will be adding the about us page where user can know how and why we were helping them.
Please assign this me under gssoc , i would like to work on this.
Thank You

Add Code of Conduct

We recommend that every repo has a code of conduct. If you don’t feel comfortable creating your own Code of Conduct from scratch we highly recommend using one of the templates provided by GitHub. If you do use a template, please read through the template and ensure that you can and will abide by the Code of Conduct.

Please follow these instructions on how to add a Code of Conduct.

Sample: https://github.com/Recode-Hive/Stackoverflow-Analysis/blob/main/CODE_OF_CONDUCT.md

💡[FEATURE]: Add Login Page

Is your feature request related to a problem? Please describe.
NA

Describe the solution you'd like
I would like to add a Login/Sign Up Page in the navbar on the top. Kindly assign this issue to me @Abidsyed25

Describe alternatives you've considered
NA

Additional context
NA

🪲[Bug]: Error Invalid DOM properties fill-rule and clip-rule.

Describe the bug
Error in SVG under Social.tsx , where in path of svg, its fill-rule and clip-rule.

To Reproduce
Steps to reproduce the behavior:
This error can be seen easily on the console of the browser.

Expected behavior
Nothing

Screenshots

Desktop (please complete the following information):

• OS: Windows 11
• Chrome Browser
• Version : 125.0

I am contributing under gssoc, and can also contribute on the same.

💡[FEATURE]: Footer for the website

Is your feature request related to a problem? Please describe.
This website needs a footer with a copyright icon and year.

📝[Docs]: Contribution guidelines

I want to add docs on how to make the PR as it is not defined in the docs.

(query) would it be okay to have it in Readme? or is it good in contribution.md

💡[FEATURE]: Add an Contact Page

Add a Contact Page

Is your feature request related to a problem? Please describe.
Users often struggle to find ways to get in touch with our team. Without a dedicated contact page, it becomes challenging for users to reach out for support, provide feedback, or make inquiries, leading to a poor user experience and potential loss of engagement.

Describe the solution you'd like
A clear and concise description of what you want to happen.
I would like to have a dedicated Contact Page on our website that provides users with various methods to reach us.

I would be really thankful if you assign me this issue as a part of GSSoC'24 @Abidsyed25 .

Missing Code of Conduct File in Repository

Currently, the repository lacks a Code of Conduct file, which is an essential component for fostering a healthy and inclusive open-source community. A Code of Conduct serves as a guideline for expected behaviour, ensuring that contributors and participants feel safe, respected, and valued within our community space.

Please assign this issue to me.

Moving border Animation

💡[FEATURE]: Create custom 404 not found page for your website

Is your feature request related to a problem? Please describe.
Create a custom 404 not found page for your website

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
now the error page looks like

💡[FEATURE]: Workflow for Closing Old Issues

Is your feature request related to a problem? Please describe.
Over time, repositories can accumulate a large number of open issues, including some that may no longer be relevant or actively worked on. Manually closing these old issues can be time-consuming and tedious.

Describe the solution you'd like
I would like a workflow that automatically identifies and closes old issues based on certain criteria, such as no recent activity or being open for a specific duration.

Add aurora background

Is your feature request related to a problem? Please describe.
Aurora bg using aceternity

Describe the solution you'd like

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

💡[FEATURE]: Automatic Comment on Pull Request Raised

Is your feature request related to a problem? Please describe:
Pull requests (PRs) are an integral part of collaborative development workflows. However, sometimes the significance of a PR or its context may not be immediately apparent to reviewers. This lack of context can lead to misunderstandings or delays in the review process.

Describe the solution you'd like:
I would like to see an automatic comment feature implemented that triggers whenever a new pull request is raised. This comment would provide essential context about the changes proposed in the PR, including details such as the purpose of the changes, any relevant issue or feature IDs, and any specific instructions for reviewers.

Describe alternatives you've considered:
One alternative could be manually adding context to each PR description. However, this approach is prone to oversight and may not be consistently applied across all PRs. Another option could be relying solely on the PR title or commit messages for context, but these may not always convey the full scope or intent of the changes.

Additional context:
Having an automatic comment added to each newly raised PR would streamline the review process by ensuring that reviewers have all the necessary information upfront, reducing the need for back-and-forth clarification. Additionally, it would improve transparency and accountability within the development team by documenting the rationale behind each set of changes.

💡[FEATURE]: Auto Commenting feature for PR Merged

Is your feature request related to a problem? Please describe.
Yes, the feature request is related to a problem. When pull requests (PRs) are merged in a project, it is often important to provide consistent feedback or notifications to the contributors. Currently, this process can be manual and time-consuming, leading to inconsistent communication and delayed acknowledgments. This can frustrate both maintainers, who have to remember to comment, and contributors, who might feel their efforts are not promptly recognized.

Describe the solution you'd like
To enhance our communication and acknowledgment process, we're implementing an auto-commenting feature for specific events within our project repository. This feature will automatically generate comments under the following circumstances:
PR Merged: Upon the successful merging of a pull request (PR), an auto-comment will be added to the corresponding issue, indicating that the PR has been merged and expressing gratitude to the contributor for their valuable contribution.

💡[FEATURE]: Improving home page

Is your feature request related to a problem? Please describe.
I would like to imporove the home page

Describe the solution you'd like
Firstly i would change the text color because it's apperance is really low and try to add some space theme background or some good background to match the vibe plain black background doesn't suit well

Screenshot

💡[FEATURE]: Hover effect in the submit button

Hey i would like to add the hovering effect in the submit button in the contact page .

Login feature

I would like to add a feature where user login first then able to access website.
Please assign me this issue under GSSoC'24.

💡[FEATURE]: Add the footer

Hey i would like to add the footer in the website where there will be the navbar links ,git links ,social media lnks , leagal privacy policy and all which make the website more proffesional

Please assign this me under gssoc .
Thank You!

Girlscript Summer of Code Introduction/Tracking

👋 Hi @Abidsyed25 ,

I am Sanjay, program Manager Girlscript Summer of Code. I'll be collaborating with you on preparing your repo for GSSoC'24 Program

Why are these changes required?
After Analysing last year's contributions and feedback it would be great for students to have a couple of standard readme files on the repo to understand what the project is all about and some issues detailing what they can contribute. This will help you to see increased engagement in your repository as well.

As mentioned students get a chance to learn step by step, how to build this project as well as invite mentors to collaborate and add features to this repo. I will generate issues, which will provide guidance on how to prepare your repo for Girlscript summer of code 2024 on 10th May.

This issue will serve as a tracking issue to track all issues related to GSSoC'24. I recommend creating a new branch for every issue and opening a pull request to track changes so we can effectively collaborate with each other and merge changes when you and I feel like those changes are ready to be merged on your primary branch.

If you have any questions or concerns, please feel free to leave a comment on this issue or any of the other issues that are generated.

I look forward to working with you

• #10
• #9
• #8
• #7
• #6

Missing Learn.md File

ScrapQuest should have a LEARN.md file to teach student how to build your project step by step. You can explain how to build your project with text, code snippets, images, or even short (5 minute) long video lessons.

Add templates for issues

Issue templates are very helpful for a collaboration repo. When users identify a bug or want to add a new feature, you can provide templates so you can collect all the pertinent information you need to fix a bug or add a new feature.

We recommend creating a “Report Bug” and “Feature Request” issue template.
you can refer this: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

Some suggested prompts/questions you can add to a “Report Bug” template are:

Briefly describe the bug
What is the expected behavior?
Please provide step by step instructions on how to reproduce the bug
Some suggested prompts/questions you can add to a “Feature Request” issue template are:

Briefly describe your feature request
What problem is this feature trying to solve?
How do we know when the feature is complete?

Reference: https://github.com/Recode-Hive/Stackoverflow-Analysis/issues/new/choose
Click on Get Started button and copy the template to yours.

complete functionality is missing on vercel

The website runs perfectly on local machine but not on vercel. Probably due to 50mb file restriction on vercel serverless edge function.

Text animtion for better UX

Add Topics

In GSSoC'24, GitHub Topics will help the discoverability of your project.

I see that you already have great topics on your repository!
I would recommend adding the name of the company like the software you use to build like "vs-code, ghdesktop" to improve your discoverability.

If you are happy with the topics you have, feel free to close this issue. 👍

💡[FEATURE]: Adding a FAQ Page

Is your feature request related to a problem? Please describe.
I want to add a FAQ page in the website. Kindly assign this issue to me @Abidsyed25

Describe the solution you'd like
NA

Describe alternatives you've considered
NA

Additional context
NA

💡[FEATURE]: Auto Commenting feature for PR Raised

Is your feature request related to a problem? Please describe.
Yes, the feature request is related to a problem. When contributors raise pull requests (PRs) in a project, it is crucial to provide immediate acknowledgment and feedback to encourage collaboration and maintain transparency. However, manually commenting on every PR can be time-consuming for maintainers, leading to delays and inconsistency in communication. This can result in contributors feeling undervalued or discouraged from further participation.

Describe the solution you'd like
This solution introduces a new GitHub Actions workflow that automatically comments on new and updated pull requests. This feature aims to streamline the contribution process by providing contributors with immediate feedback and guidance upon creating or updating their pull requests.

💡[FEATURE]: Add a favicon to the website

Is your feature request related to a problem? Please describe.
The website doesn't have a favicon. It needs a favicon for symbolic representation of the website

Describe the solution you'd like
I would like to add a favicon to the website which will represent the view of the website.

Additional context

💡[FEATURE]: Auto Commenting when an issue is closed by maintainer

Is your feature request related to a problem? Please describe.
Yes, the feature request is related to the problem of lack of communication and acknowledgment when issues are closed in the repository. Contributors may feel neglected or uncertain about the status of their issues if they are closed without any feedback or acknowledgment. This can lead to frustration and a decrease in motivation to contribute further.

Describe the solution you'd like
The solution is to automatically post a comment on the issue whenever it gets closed. This comment should thank the issue creator for their contribution and inform them that their issue has been closed. The message can include the issue number and a friendly greeting to make it more personal. This automation ensures that every closed issue receives a consistent and timely response, improving communication and contributor experience.

Learn.md

Learn repos should have a LEARN.md file to teach student how to build your project step by step. You can explain how to build your project with text, code snippets, images, or even short (5 minute) long video lessons. As the maintainer of a Learn repo, the LEARN.md file requires you to think critically about how to explain the building of your project and how to also make it engaging. We don't expect you to be an expert teacher, but we would like you to reflect on how difficult it was to get to your level of knowledge, and then provide friendly guidance to help other students to learn.

Reference: https://github.com/Recode-Hive/Stackoverflow-Analysis/blob/main/Learn.md

💡[FEATURE]: Contact Information Section

Is your feature request related to a problem? Please describe.

I'm always frustrated when users have difficulty finding our contact information on the "About" page. This often leads to confusion and reduces user engagement as users are unsure how to reach out for support or inquiries. The current layout does not highlight your contact details prominently, making it inconvenient for users to get in touch.

Describe the solution you'd like

I would like to add a dedicated Contact Information section towards the bottom of the "About" page. This section will clearly display your contact email and phone number, styled consistently with the rest of the page. The contact details should be easily accessible, ensuring that users can quickly find how to reach you. The email address should be a mailto link, and the phone number should be a tel link, allowing users to interact with these details seamlessly.

Describe alternatives you've considered

• Placing Contact Information in the Footer: Instead of adding a dedicated section on the "About" page, placing contact details in the footer of every page. However, this could clutter the footer and might not be as prominently visible as a dedicated section.

• Using a Contact Form: Implementing a contact form on the "About" page where users can directly submit their inquiries. This adds complexity and requires more maintenance compared to displaying simple contact details.

• Including Contact Info in a Sidebar: Adding a sidebar with contact information on the "About" page. This could impact the page layout and user experience, especially on mobile devices.

Additional context

Adding a Contact Information section will not only improve user experience but also enhance the professionalism of your website. Users will appreciate the easy access to support and inquiries, potentially increasing engagement and satisfaction.

Example Layout:

import React from 'react';
import { Nav } from "@/components/Nav";
import Footer from '@/components/Footer';

const About: React.FC = () => {
  return (
    <div className="relative">
      <Nav />
      <div className="container mx-auto p-6 max-w-[48rem]"> {/* Added max-w-lg for reducing the box size */}
        <h1 className="text-4xl font-bold mb-6 text-center">About <span className="bg-[#8abf83] rounded px-2">Us</span></h1>

        <h2 className="text-2xl text-center font-semibold mb-4">Welcome to ScrapQuest!</h2>
        <p className="mb-6">
          At ScrapQuest, we make data extraction from websites effortless and efficient. Our cutting-edge solution is designed to help you quickly gather valuable information from any website without the usual hassle and complications.
        </p>

        <h2 className="text-2xl text-center font-semibold mb-4">Our Mission</h2>
        <p className="mb-6">
          Our mission is to simplify the process of web scraping, making it accessible and straightforward for everyone. Whether you're a business looking to gain insights, a researcher needing data for your projects, or a developer seeking to integrate web data into your applications, ScrapQuest is here to help.
        </p>

        <h2 className="text-2xl text-center font-semibold mb-4">What We Do</h2>
        <p className="mb-6">
          ScrapQuest offers a powerful and intuitive platform for web scraping. Our solution allows users to easily and quickly collect data from any website. We focus on providing a seamless experience that minimizes the technical complexities of data extraction, enabling users to obtain the information they need with ease.
        </p>

        <h2 className="text-center text-2xl font-semibold mb-4">Contact Us</h2>
        <p className="mb-6">
          Have questions or need support? Feel free to reach out to our team. We're here to help you get the most out of ScrapQuest.
        </p>

        <div className="text-center">
          <p>Email: <a href="mailto:[email protected]" className="text-blue-600">[email protected]</a></p>
          <p>Phone: <a href="tel:[phone]" className="text-blue-600">[phone]</a></p>
        </div>

        {/* Optional: Footer Component */}
        <Footer />
      </div>
    </div>
  );
}

export default About;

📝[Docs]: Add GitHub Desktop Contribution Instructions

What Docs changes are you proposing?
Provide a clear description of the changes you're proposing for the documentation. Are you suggesting corrections, clarifications, additions, or updates?
I am interested in contributing to the project by adding detailed instructions on how to contribute using GitHub Desktop.

Why do the Docs need this improvement? What is the motivation for this change? How will this change benefit the community?
Explain the motivation behind the proposed changes and how they will benefit the community or users of the documentation.
I believe that by providing clear and comprehensive guidance, we can encourage more contributors to participate in the project, especially those who prefer using GitHub Desktop for their contributions.

Describe the solution you'd like
Provide a clear and concise description of the changes you'd like to see implemented in the documentation.
I am interested in contributing to the project by adding detailed instructions on how to contribute using GitHub Desktop.

I believe that by providing clear and comprehensive guidance, we can encourage more contributors to participate in the project, especially those who prefer using GitHub Desktop for their contributions.

Could you please assign me the issue related to adding GitHub Desktop contribution instructions under gssoc24? I am excited about the opportunity to contribute to the project and help streamline the contribution process for others.

Describe alternatives you've considered
If you've thought about alternative approaches or solutions, briefly describe them here.

Additional context
Add any additional context, examples, or screenshots related to the proposed documentation changes.

Add issues

As the maintainer of a Collaborate repo, keeping Issues up-to-date will help the student community understand what they can do to contribute. Issues should vary by the easy (update documentation) to the difficult (add a new feature). The more involved you are, the more opportunities there are to collaborate.

Recommendations:

Add issues of varying difficulty to the repo often. you must add the tag gssoc, Level 1, Level 2, Level 3 good first issue etc.
How we cacluclate the Scores on Leaderboard: Every PR one point
Level 1: 10 points
Level 2: 25 points
Level 3: 45 points
Try to add some documentation issues as well it would be easy for beginner contributor to explore opensource through your repo.
Generate issues even if you plan on solving them, so the repository appears as active.
Contribute/commit often to the repo so it does not go stale.
Reference https://github.com/Recode-Hive/Stackoverflow-Analysis/issues

Improving the UI of the landing page

@Abidsyed25 I would like to improve the UI of the landing page. Please assign me this task under GSSoC'24.

Add loader to webpage

Is your feature request related to a problem? Please describe.
Adding a loading animation after we click

Describe the solution you'd like
there is no loading animation or component for this, will be adding that

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

💡[FEATURE]: Create the logo fro ScrapQuest

I want to create the logo for Scrap Quest .
Please assign this me under gssoc i would like to work on this.

Missing CONTRIBUTING.md File in Repository

The repository currently lacks a CONTRIBUTING.md file, which is an important resource for guiding potential contributors on how to engage with the project effectively. A CONTRIBUTING.md file outlines the contribution guidelines, coding standards, and procedures for submitting pull requests, thus streamlining the contribution process and ensuring consistency across contributions.

Could you please assign this issue to me under GSSOC 24.

💡[FEATURE]: Workflow for closing Old PRs

Is your feature request related to a problem? Please describe.
Over time, open pull requests (PRs) can accumulate in a repository, cluttering the interface and making it difficult to focus on active development tasks. Additionally, outdated or abandoned PRs may no longer serve their intended purpose and should be closed to maintain repository cleanliness.

Describe the solution you'd like
Implement a workflow that automatically closes old PRs based on predefined criteria, such as their last update timestamp. By regularly closing PRs that have not been updated within a certain timeframe, the repository can stay organized, and contributors can focus on active and relevant PRs.

💡[FEATURE]: Create a dockerfile for the project

I want to dockerize the app so that in future when someone fork the repo in different nodejs environment then he can easily use the app. Docker makes it easy to run the add in a single command.

💡[FEATURE]: Auto Commenting Feat for Issue Creation

Is your feature request related to a problem? Please describe.
Yes, the feature request is related to a problem. When issues are created in a project, it is important to provide immediate acknowledgment and guidance to the issue creator. However, manually commenting on every newly created issue can be time-consuming for maintainers, leading to delays and inconsistency in communication. This can result in contributors feeling ignored or discouraged from further participation.

Describe the solution you'd like
I would like an automated feature that posts a predefined comment on an issue as soon as it is created. This comment could include acknowledgment of the issue, guidelines for further steps, or any other relevant information. The automation should be customizable to accommodate different project workflows and communication styles.

💡[FEATURE]: implement the scrape the website images

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

their is an the feature that are enable user to fetch the images from the website that they required

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

please assign me this issue

💡[FEATURE]: Add Navigation Menu in the top of the website

Is your feature request related to a problem? Please describe.
Currently there is no navigation menu present in the website, which is an essential thing needed in any website to navigate between webpages.

Describe the solution you'd like
I would implement a clean, visually attractive navigation menu by making use of ShadCN UI components.

@Abidsyed25 please assign me this issue as part of GSSOC'24. Thank you!

Reduce API response time for puppeteer service

It looks like the service is taking longer to respond than what's allowed in the free tier of Vercel Functions, resulting in a timeout error. To address this, we'll need to make some changes to the architecture. If anyone is interested in this issue, please reach out to me so we can discuss the approach.

Issue template is not working

Issue template for this project is not working as expected. Check the code and correct it.

💡[FEATURE]: Dark Theme

Is your feature request related to a problem? Please describe.
I'm always frustrated when using the web app for extended periods, especially in low-light environments or at night. The bright, white background causes eye strain and discomfort, making it difficult to focus and increasing fatigue. Additionally, the lack of a dark theme makes the app less visually appealing and less in line with modern user interface trends, which many users prefer for its aesthetic and ergonomic benefits.

Describe the solution you'd like
I would like the web app to offer a dark theme option. This theme should replace the bright, white backgrounds with darker shades (e.g., dark grey or black) and adjust text and other UI elements to ensure readability against the dark background. Ideally, the dark theme should be easily switchable from the settings menu or even automatically triggered based on system-wide settings (e.g., following the device’s dark mode settings). This will help reduce eye strain, enhance focus, and improve the overall user experience, especially in low-light conditions.

@Abidsyed25 please assign me this issue

💡[FEATURE]: Add a Pull Request Template

Describe the feature

Often, pull requests lack necessary details, making it difficult for reviewers to understand the changes, the reasons behind them, and how to test them. This can lead to delays in the review process, increased back-and-forth communication, and potential oversight of critical issues.
The solution is to implement a standardized pull request template. This template should include sections that prompt the author to provide essential information, such as:

• A brief description of the changes.
• The issue or feature being addressed (linked to relevant issue tracker entries).
• Screenshots or GIFs (if the changes include UI modifications).
• Checklist for confirming code adheres to coding standards, tests are added/updated, and documentation is updated.

Add ScreenShots