Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

E-commerce product page

sass/scss
Maxessien•140
@Maxessien
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'm most proud of how I structured and organized my HTML and JavaScript to ensure both accessibility and responsiveness across devices. The custom-built lightbox and interactive cart logic challenged me, and completing them without any external libraries felt very rewarding.

Next time, I would approach the JavaScript logic with better modularity in mind—breaking functions into smaller, reusable parts. I would also incorporate more testing for edge cases, especially when handling user interactions like rapid clicks or invalid states in the cart.

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

One major challenge I encountered was managing the cart state and ensuring it updated accurately when users added, removed, or toggled items. Initially, my logic didn’t handle multiple item additions correctly, and removing items would sometimes break the layout.

To overcome this, I broke the problem down into smaller parts—first isolating the logic that adds items, then the one that updates the display, and finally the one that handles removal. I also used console.log() frequently to debug state changes and DOM updates, which helped me trace the issues step by step.

Another challenge was building the lightbox gallery to open and close correctly while syncing thumbnail selections. I carefully studied how event delegation and class toggling work and used that knowledge to fix issues with overlay closing and image swapping.

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

I would appreciate feedback on the following areas:

  • Accessibility best practices: I’ve added basic aria-labels and ensured keyboard navigability, but I’m not entirely confident everything is as accessible as it could be. I'd love advice on how to improve this, especially regarding the lightbox gallery and cart modal.

  • JavaScript optimization: Are there parts of my JavaScript that could be simplified or written in a more efficient way, especially regarding event delegation or state management for the cart and lightbox?

  • Responsive design refinements: The layout works on mobile and desktop, but I'm not sure if I’ve used the most scalable or maintainable approach for responsiveness. I’d appreciate insights into how I could make it more robust or efficient using modern CSS techniques.

  • CSS structuring: I'm currently using utility classes and custom properties. Any tips on better organizing my CSS or making it more reusable would be helpful.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

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