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

Used Fetch API, Local Storage, DOM manipulation, CSS, and GitHub Pages

accessibility, animation
Deepu23456•110
@Deepu23456
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’m most proud of how I dynamically managed the cart and UI updates using JavaScript, ensuring a smooth user experience with real-time updates. Successfully integrating local storage to persist cart data and deploying the project using GitHub Pages was also a highlight.

Next time, I would optimize the state management by using a framework like React for better scalability and maintainability. Additionally, I would improve accessibility and enhance the UI further with animations and better responsiveness.

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

One major challenge was ensuring the cart state persisted correctly and updated dynamically. Sometimes, items wouldn't reset properly after clearing the cart. I overcame this by carefully managing local storage and ensuring state updates were reflected in the UI.

Finally, pushing the project to the correct GitHub account caused permission issues. I fixed this by properly configuring Git credentials and ensuring I was using the right account for authentication.

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

specific improvements, like optimizing performance, refining the UI/UX, fixing bugs, or adding new features

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Deepu23456'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

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.