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

Responsive Mobile-first product-list-with-cart-main

Barbara Ward•1,160
@bward67
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?

Did my eyes read this challenge level correctly? JUNIOR! I had completed all the Jr ones and was more than half way through the intermediate level challenges when I saw this one pop up as "new". I thought it would be a breeze but... not so much.

I was able to do the HTML, CSS and some of the JS but then I got a bit lost! So I searched YouTube for help and found this from CodeExplained: https://www.youtube.com/watch?v=UcrypywtAm0&t=1560s and it was exactly as it said on the tin - the code was explained ... BEAUTIFULLY! I had to watch it MANY times and practice it "in my own code" for a few days - but I LOVE what I learned from him.

The first thing I did after fetching the data from the API was to give each object in the array an id. I did this by doing a forEach on the array and setting 2 parameters: item and index like this: dataArray.forEach((item, index) => { item.id = index + 1; });

I used .toFixed(2) to get 2 decimal points after the price as it was inconsistent once I displayed the products from the API.

The key for being able to calculate the number of items in the cart was to create a new key - value object pair in the array called: numberOfUnits and = it to 1. I did this using destructuring. I also had to do this for the number in the red button which pops up when the user clicks the Add to Cart button.

I know my code is very messy and juvenile in some areas but this was a great learning experience for me.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Barbara Ward's solution.

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 1st-party linked stylesheets, and styles within <style> tags.

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.