This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying pages/index.js. The page auto-updates as you edit the file.

API routes can be accessed on http://localhost:3000/api/hello. This endpoint can be edited in pages/api/hello.js.

The pages/api directory is mapped to /api/*. Files in this directory are treated as API routes instead of React pages.

This project uses next/font to automatically optimize and load Inter, a custom Google Font.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.

WIICAMP's Intern Template

Deisgn:

Figma

Packages can be used

  1. Swiper: for slider.
  2. Axios: for calling api
  3. Bootstrap: you can (only) use the bootstrap classes, by import the CSS's Link of Bootstrap. No need to install the whole packge to the project.
  4. classnames / clsx: For merging classes.
  5. React-hook-form and Yup for validation.
  6. Icons: use icons from lucide icon.
  7. cookies-next

If you want to use any packages, please confirm to me first.

Point of review

  • Perfect Pixel Alignment with Figma Designs.
  • Clear and Organized Folder Structure.
  • Correct HTML structure: Ensure that the HTML structure is correct and follows standards. Use basic HTML tags such as , , , and make sure they are properly closed.
  • Appropriate use of HTML tags: Check whether HTML tags are used with meaningful and appropriate purposes. Do not use tags for purposes other than their intended use.
  • Proper tag count: Ensure that there are no extra or missing HTML tags. Make sure each opening tag has a corresponding closing tag.
  • Readability and maintainability: Check if the code is readable. Are variables, comments, and naming conventions used appropriately to make the code maintainable?
  • Use of ESLint: Check if the code complies with ESLint rules. Ensure there are no errors or warnings from ESLint.
  • Interaction with Next.js: If the code uses Next.js, ensure that all Next.js features are used correctly, such as routing or server-side rendering.
  • Browser compatibility: Check that the code works on various browsers and doesn't cause errors or incorrect display on specific browsers.
  • Compliance with interaction rules: Ensure that the code adheres to user interaction rules, such as mobile-friendliness and interaction security.

Flow of working

Please fork the source code to your repository. Then estimate your time for each task/section of the website.

For more details. don't hesitate to contact

Note for windows's user

If you are using windows, please change the size of the screen view to 1457px, by that your html's body will be 1440px.