Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 12 months ago

Responsive Ecommerce Landing Page TailwindCSS ReactJS Vite

react, tailwind-css, vite
lavollmer•440
@lavollmer
A solution to the E-commerce product page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I am most proud of working through the different challenges and expanding my knowledge of useState, props, flexbox, and styling options. Next time, I would focus more on the functionality of the application and then addressing the styling pieces.

What challenges did you encounter, and how did you overcome them?

I worked through the mobile responsive challenge, useState knowledge, flexbox styling, sidebar navigation in mobile and much more. I worked through each one individually - taking time to understand my gaps of knowledge. Overall, it was a great project.

What specific areas of your project would you like help with?

I would like help with creating the functionality for the delete trash icon in the cart. I would like the icon to remove all information when selected with the statement "Your cart is empty".

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mesroua Djamel•430
    @MesrouaDjamel
    Posted 10 months ago

    congratulations for your design it's close to the proposed design i have some suggestion to propose you : The carousel : you can use material tailwinds: https://www.material-tailwind.com/docs/react/carousel it's easy to set up and the component is animated. Hover: https://tailwindcss.com/docs/fill

    and use this syntax in jsx => <svg width="57” height="54” viewBox="0 0 57 54” fill="none” className="absolute left-4 top-[200px] cursor-pointer stroke-veryDarkBlue hover:stroke-orange transition-all ease-in-out duration-300” onClick={handlePrev} > <ellipse cx="28.1706” cy="27.1216” rx="28.1706” ry="26.7823” fill="#FEFFFF” stroke="none” /> <path d="M33.8049 16.4087L22.5366 27.1216L33.8049 37.8345” strokeWidth="3” /> </svg> check if the svg already has a fill or stroke and delete it

    Trash: const handleDelete = () => { if (quantityToBuy === 0) { setIsAddedToCart(false); } setIsAddedToCart(false); setIsCartOpen(false); setQuantityToBuy(0); };

    Translated with DeepL.com (free version)

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub