Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

E-commerce product page challenge hub build using React

react, itcss
Mohamed•325
@MohamedBehhar
A solution to the E-commerce product page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I tried to use react to build this challenge, i think i kind of made it but i have a problem when sliding between the product images, it looks like some element of the pages are getting selected.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Shashree Samuel•8,860
    @shashreesamuel
    Posted over 3 years ago

    Hey MohamedBehhar, good job on completing this solution keep up the good work.

    Your solution looks good on the right path however I have some suggestions

    • The product name needs some margin-top

    • The font size of the product name needs to be a bit bigger

    • The description of the product needs some line-height.

    • The price with the strikethrough needs some margin-top

    • The width of the button should be a bit smaller

    • The color of the button should be a darker orange.

    • The color of the title should be a darker orange. I recommend referring to the style-guide.md file to be sure

    • The color of the "50%" should be a darker orange.

    In terms of your accessibility issues, simply wrap all your content between <main> tags to get rid of all accessibility issues.

    In terms of your validation errors, a <p> tag is not allowed to be a child of the <button> tag.

    I hope this helps

    Cheers Happy coding 👍

    Marked as helpful
  • P
    Zak Schenck•40
    @ZakSchenck
    Posted over 3 years ago

    @TheCoderGuru gave excellent feedback, but I'd like to also suggest adding a notification for when the cart has items in it. I would have never known it had items in it until I checked. I did this by adding a container for the cart image and notification, then setting the position of the notification to absolute and positioned it to my liking. There are more way to do it though.

    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

Oops! 😬

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

Log in with GitHub