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

Product list with cart using React | Tailwind

react, tailwind-css, accessibility
Mazen Hassan•600
@Mazz100
A solution to the Product list with cart 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 really grateful that I kept going till the end, even though I got stuck for an extended period and took longer than expected to finish the challenge but I finally did it.

I received a lot of help along the way, and I went through many rounds of refactoring and cleaning up messy code. Despite the time it took, it was a great learning experience.

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

I faced difficulty with the approach of mapping list and passing props with unique key and as result I had all the code separate and meaningless, to overcome it I mapped the product data directly into `` as the child allowing for easy prop passing, then created 3 functions in App.jsx to handle all cart updates.

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

I am open for any feedback offered, I already asked for enough help from community and I just need to get a better idea on how React works and read docs more often. Thanks for taking a look at my solution :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Fallou Jeng•540
    @falloumacbook
    Posted 12 months ago

    Nice work as always man, it would be great if you move the cards a little bit left.

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