Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 7 months ago

E-commerce product page built with React and TailwindCSS

accessibility, react, tailwind-css, typescript
Jenny Eikens•250
@Jenny-Eikens
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 am proud of my implementation of the image gallery and the lightbox.

I also feel good about the fact that, in this project, I put the data into separate files to reference from the components, which is something I only just learned to do from feedback on my previous project (where I had hard-coded the data).

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

There were a lot of things I struggled with, as this was definitely the most advanced project I have done so far.

This is definitely a good thing though as I learned a lot. I had never coded an image gallery and a lightbox before. I also didn't feel super confident passing down state variables before this project, but now I feel like I really got the hang of it.

At first I felt overwhelmed by all the functionalities I would have to implement, but the more I thought about it and came up with a structure and ideas, the more confident I felt that I would be able to do it.

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

My one main issue is with centering the open shopping cart on mobile screens. I positioned it absolutely, which works for bigger screens, but I just haven't been able to figure out how to center it on the page on small screens. I don't want to use a fixed position because I don't want it to cover the other content when I scroll. Someone please tell me how to solve this issue, as I know my current solution to this isn't a good one.

Another thing I haven't managed to figure out is how to prevent the nav links from moving up a little to accommodate for the added border at the bottom upon hovering.

Other than that, I don't have any specific questions right now, but any feedback is welcome!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Jenny Eikens's solution.

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.