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

e-commerce page

tortaruga•790
@tortaruga
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?

It works! The code is a bit messy but I'm happy that it works

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

I struggled with the mobile menu, the cart menu, the lightbox, the general layout, making each button do whatever each button had to do, it'd be quicker to ask what i didn't struggle with. but my perseverance will triumph. I bend, but do not break. I whine, and complain, and cry and throw tantrums, but eventually, by sheer luck, through some deus ex machina and never through my actual skills, I reach my goal. i'm so sorry for anyone who actually reads these i'll stop wasting your time

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

is there an easier way to make that side menu thing so that the rest of the screen gets darker and paler when it is open? right now i use a dialog for the menu, and style the rest of the content through js whenever the dialog is showing, because the ::backdrop only works if i make the dialog a modal, but if it is a modal it doesn't stay styled at one side of the screen, but it appears in the center no matter which saint I light a candle to.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • coder-abdo•280
    @coder-abdo
    Posted about 1 year ago

    your solution is amazing, I love the way you handle the entire application only using native javascript so you have done great, but here are little notes:

    • you can make the overlay when clicking the menu icon by using z-index with a high value to cover the whole application.
    • the lightbox has a vertical scrollbar you need to remove it and you can use overflow: hidden to prevent this problem. you did an amazing job.
    Marked as helpful

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.

Oops! 😬

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

Log in with GitHub