im working on the signup page as i have worked on similar projects in react

Check the Figma design and create the footer for our website. Make sure that it's responsive for smaller screens.

The "Explore" button of the join us cards is not getting fully rendered as shown due to a minor mistake in CSS.

Currently , the landing page gets duplicated

due to the presence of

    { <Navbar />
      {isLoading ? <Spinner /> : <LandingPage />}
      <Router>
      <Routes>
        <Route exact path="/" element={<LandingPage />}/>
        <Route path="/signup" element={<Signup />} />
      </Routes>
    </Router> 

      {isLoading ? (
        <Spinner />
      ) : (
        <Router>
          <Navbar />
          <Routes>
            <Route exact path="/" element={<LandingPage className="z-[-5]" />} />
            <Route path="/signup" element={<Signup />} />
          </Routes>
        </Router>
      )}
      
      

The required code should be

  {isLoading ? <Spinner /> : 
      <Router>
        <Navbar />
      <Routes>
        <Route exact path="/" element={<LandingPage />}/>
        <Route path="/signup" element={<Signup />} />
      </Routes>
    </Router>
      }
      

I would like to work on this issue

A horizontal scroll bar in a website is not an example of a good UX. As you can see in the attached screenshot, there's a scroll bar at the bottom of the page which must be taken care of.

Find the ACM JEC logo and create a favicon for the same as shown in the attached screenshot.

Create the 4 cards using a reusable utility component and ensure responsiveness in them.

Currently, our project lacks standardized issue and pull request templates, making it challenging for contributors to provide essential information when creating issues or pull requests.

Proposed Solution:

• Add clear and concise instructions on how to create issue and pull request templates for our project.

Instructions for Contributors:

To add issue and pull request templates to our project, follow these steps:

1. Create a .github directory: Start by creating a .github directory at the root of our repository if it doesn't already exist.

2. Inside the .github directory , create one subdirectory named ISSUE_TEMPLATE for issue templates and one filed named PULL_REQUEST_TEMPLATE.md for pull request templates.

3. Create issue templates: Inside the ISSUE_TEMPLATE directory, create one or more Markdown files (e.g., bug_report.md, feature_request.md) representing different types of issues. These files will serve as templates for contributors to use when creating issues. You can provide a basic structure, headings, and guidelines in these templates.

4. Create a pull request template: Inside the PULL_REQUEST_TEMPLATE.md file that contributors can use as a template for their pull requests. Include sections for a description, context, and a checklist for tasks that need to be completed.

Additional Information:
Feel free to ask any questions or seek clarification if you encounter any issues while implementing these instructions.

Create the category section and make sure to make it responsive for all screens.

Create this section. Refer the Figma design for more details.

Add a beautiful hover effect to the join us cards.

Create the team section which houses the details of the team members of ACM JEC. Ensure that it is fully responsive.

Refer to the Figma design provided in the Readme file and create the navbar component (preferably using TailwindCSS).

Our project currently lacks a well-defined README.md file in the repository, which makes it challenging for potential contributors to understand the project's requirements, and how to get started.

Proposed Solution:

Edit the current Readme.md file to include information about Hacktoberfest, project prerequisites, instructions for setting up the local development environment, and guidelines for contributing to the project.

Instructions for Contributors and Guidelines for Readme

• Project Introduction: The README should begin with a brief introduction to the project. and include a link to the Figma design for the project.

• Hacktoberfest: Mention that this project is participating in Hacktoberfest and provide a link to the official Hacktoberfest website for contributors to learn more and sign up.

• Prerequisites: Include a section that lists the prerequisites for contributors. Mention that they should have Node.js and npm installed.

• Getting Started: Provide clear and detailed instructions for setting up the local development environment. Include commands for cloning the repository, installing dependencies, and starting the development server.

Want to add frontend and Docker Image of Website

Refer to the Figma design and create a fully responsive 'upcoming events' section.
Check the attached screenshot for reference:

Refer to the Figma design provided in the Readme file and create the landing page component (preferably using tailwindCSS).
Ensure responsiveness and write clean code. Create separate components for landing page UI and use them together in the LandingPage.jsx file.

Fix the text positioning of the word "chapter" in the landing page:

Fix the positioning of the explore button of the 4th card:

The UI for the signup page is completed but currently it is non-functional. Using OAuth, add authentication to the signup page.

I would like to add a section that shows the numbers of students who have currently registered on the platform, in order to attract more users

Create a spinner that spins until the page is rendered.
HINT - You will need to use conditional rendering the page component.

Create success stories component and use the provided images ONLY.

As per the Figma design, create the 'previous events' section. Preferably make a responsive card and dynamically render it in a carousel.

Check the pull requests #7 and #9. Merge both of the codes so that the landing page as well as the join us section both get rendered. Currently, only the landing page is visible and the join us section from the previous PR has disappeared.

All you need to do is clone the landing page and the join us section PRs (#7 and #9) separately and then merge both of them in such a way that both the components get rendered and not override one another as shown in the attachment.

The 4 cards should be below the "why join us" title.

At the moment, Navbar and Landing page are not synced properly. Fix it.