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

Responsive Product List with Cart using CSS Grid/Flexbox/JavaScript

accessibility
Elizabeth Sotomayor•230
@elizabethrsotomayor
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 most proud of the functionality and responsiveness of the app. Everything works the way I wanted it to, I love the design and how the app looks on both mobile and desktop devices. I'm also proud of the way I was able to dynamically create the cart items through use of a Document Fragment. Next time I would like to try working with a framework like React or JQuery to complete a project.

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

I encountered a problem with the cart total overlapping when the item was added to the cart but I used absolute positioning to prevent overlap. I had an issue with the quantity of items carrying over when the "Start New Order" button was clicked and fixed it by manually setting the quantity back to 1 whenever an item is added to the cart with a new order.

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

I would like help with the use of the Document Fragment. In my project, I reused a Fragment twice to create the items in the cart and order confirmation and I am wondering if this is a common practice to reuse the Fragment. I feel like when each item is dynamically created my code looks a bit repetitive with the use of createElement and setAttribute for each item so I'm wondering if there's a better/cleaner way to go about populating the cart/order confirm modal.

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 Elizabeth Sotomayor'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 all CSS, SASS, 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.