Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 30 days ago

E-commerce product page

react
Ghozy•280
@Ghozy165
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?

the most thing i proud is that i can complete this project and complete this project using react and react hook

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

Using React Hooks to store values, I encountered many errors. I searched for resources on the internet to learn how to use Hooks, but eventually, I just asked an AI how to use react hook step by step. After that, I stopped getting errors."

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

There are still many parts that are lacking. If anyone wants to comment, thank you.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    toshirokubota•1,320
    @toshirokubota
    Posted 25 days ago

    Congratulations! Your design looks very nice. You paid attention to details and painstakingly reproduced some subtle designs, like the underscore on the route in <nav>, outline on the selected thumbnail, etc. I have noticed a few behavioral issues you may want to look into. First, when I open the lightbox and shrink the window to the tablet size, the foreground merged into the background behind the lightbox screen. I think you are disabling the lightbox feature for small screen sizes, and in real life, the user would not continuously shrink the screen. But it looks strange and I think a small state change will be able to fix it. Second, somehow, the loading of images was slow. It could be something fixable but I am not sure how. Third, when the "checkout" button is clicked, nothing happens. I know that we are not implementing real checkout, but at least you can close the modal and clear the cart. Well, these are something I noticed while playing with your app. Again, great job and happy coding!

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