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

E-Commerce Product Page (JS/SCSS)

accessibility, bem, sass/scss, lighthouse
Bartosz Dudziak•720
@bartoszdudziak-dev
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?
  • My solution is not perfect and it was exhausting for me.
  • I am proud of I managed to create all given features. I also added some on my own.
  • I would definitely think about better structure of my code next time because I wrote in a single file and it became a bit messy.
  • I implemented basic accessibility.
What challenges did you encounter, and how did you overcome them?
  • The most problem was to create overlay. It did not work on my fixed positioned elements so I created their own overlay for each one. That solution could be better.
  • Positioning the elements took me the most time.
What specific areas of your project would you like help with?

Please give me some opinion or advice. 🫡

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Achara Chisom Solomon•490
    @AcharaChisomSolomon
    Posted about 1 year ago

    Heyyy @bartoszdudziak-dev,

    Great Job on completing the challenge, and I love how you split your css files.

    The only feedback I have is that you should check out 'CSS CLAMP', it could potentially reduce the amount of media queries you need.

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