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

Dynamic button-controlled e-commerce product page

P
Tuna Erten•430
@tunaerten
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?

This was quite a long project that took me about a month to complete. Unfortunately, due to holidays and my workload, I couldn't dedicate as much time as I wanted, but I'm happy to have finished it in the end. The HTML and CSS parts were fairly straightforward. In JavaScript, I spent the most time on the lightbox. Initially,

Additionally, instead of creating a product with only static text, I structured it as an array to make it appear as if the product data came from an API. I defined all the information there, which allowed me to reuse and modify the same variables across multiple places.

As for features outside the original project plans, I developed a system where items are dynamically added and removed instead of just using a standalone trash bin. (I noticed this approach is common in many e-commerce sites.) Also, items added to the shopping cart disappear after a certain period but reappear when you hover over the cart icon.

Initially, I planned to add a dark mode as well, but I decided to skip it because I wanted to finish the project. Maybe I'll implement it in my next project.

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

I wanted to use the same lightbox element for the mobile view, but when I couldn't make it work, I ended up planning it as a separate element.

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

Open to any and all suggestions

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Andi Gashi•660
    @Andigashi1
    Posted 5 months ago

    Hi i love the site and the detail to the animations, i only have a small suggestion. Add a max width for mobile so this way the image looks better on larger screens that dont include desktop view and the text and buttons too. Good luck on the next projects

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub