Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

E-commerce page with lightbox gallery and cart functionality

Luke•140
@lukeSchwade
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 pretty proud of how I set up the Add-to-cart functionality, which I planned and designed without consulting any tutorials. If I were to start over, I'd probably organize my CSS a bit better with less specific entries. I had the idea to start adding "flex-container" as a class to indicate flexboxes but I'm not sure if that's a good idea yet as it's slightly annoying to use devtools to play with flex properties when everything is relying on the same class

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

I had a really funny bug when building the lightbox where I was grabbing the "src" property of the click target, and using a function to extract the number from the filename to determine which image should be the main image (eg. if you click on an image with src of "image-thumbnail-2" it sets the index to 2 and shows main-image-2; I know, that's horrible), except I found out that VScode's live site extension adds "https://127.0.0:5500" to the front of the img src, so I had to hunt down why my index variable was randomly turning into 127 which broke the lightbox but for some reason only 30% of the time. ridiculous thing to hunt down, because I thought it was an issue with the index type being turned into a string at first.

Using chrome's live expressions tool to keep track of the variable and figure out exactly where it went wrong was tremendously useful. I ended up adding a unique class for each image and using that instead, which seems safer lol

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

I wanted to animate the cart entries so that the other ones slide up to fill the gap instead of instantly moving, but it seems that is not possible in vanilla CSS unfortunately, and I wasn't confident in my JS enough to implement it. If there is in fact a way to do that in CSS I'd love to know.

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 Luke'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.