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

A beautiful and responsive e-commerce page built in JavaScript

developer-luizcarlos•140
@developer-luizcarlos
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?

What I was most proud of was the fact that I was able to carry out a complex and extensive project from start to finish completely independently, without having to resort to any external help. I also notice my evolution in the organization of the code and how my logical reasoning has evolved in the last few months, leading me to think strategically about how to build the project structure and use each resource that the language offers in order to complete the challenge.

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

My biggest challenge was to develop a way to change images on the slide along with changing the effect on the images of product options, which gave me a solution in associating variables already created and using a function that worked both in individual click on the images to change the image on the slide.

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

I would like someone to show me how I could create an effect for the image of the options that was faithful to the design, something that I was unable to implement in the final version of my project. If you want any explanation on any point in my code, feel free to ask your question. Tips and suggestions are always welcome. Sorry for the bad english. If possible, follow me on github

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 developer-luizcarlos'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.