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

My React Ecommerce Product Page

react, tailwind-css
Aecio Neto•340
@aecio-neto
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?

I found a notes extension for VS Code that helped me organize what to do. Next time, I’ll start with a more detailed step-by-step plan and implement things gradually.

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

Biggest challenge: Lightbox Component/Effect - It wasn’t difficult to implement, but I had to pause for a bit to think and reflect on how to do it. In the end, I found the code repetitive, but it worked well.

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

How to think and plan the components? My impression is that they ended up too fragmented, but there's a logic behind them.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alex•3,130
    @Alex-Archer-I
    Posted about 1 year ago

    Hi!

    I have notice that the arrow buttons on the image isn't positioned on the center. There are two reasons for it.

    At first when you use top: 50% the element located just behind the 50% line i.e. the top of the element hits the middle but not the center. To fix it you should add transform: translateY(-50%) property.

    The second is that you use that whole container (image + thumbnails) as relative container, so it's more difficult to center them inside the image. So I suggest you to separate image with arrows and thumbnails as different components.

    Alas, I can't see the source code to answer your question about the components structure - the link leads to 404.

    But hope you'll still find that helpful =)

    Congrats with difficult challenge, good luck =)

    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

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