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

Tailwind + TypeScript + React.js | E-commerce Product Page

react, redux-toolkit, tailwind-css, typescript, accessibility
Better5afe•850
@better5afe
A solution to the E-commerce product page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi there!

This project took me a little bit longer than I expected, the autumn weather definitely does not help with my coding motivation :D

To summarize, the users are able to:

  • Add and remove items from the cart.
  • Update quantity of the cart items.
  • View the cart's content.
  • Open a modal gallery carousel by clicking on the large product image and interact with it.
  • Switch the large product image by clicking on the small thumbnail image.
  • Interact with mobile gallery by tapping the arrow buttons or swiping right or left.
  • View the optimal layout for the site depending on their device's screen size.
  • See hover states for all interactive elements on the page.

In addition to this:

  • The cart is stored within local storage, so it's fetched from there as soon as the page reloads.
  • Users can swipe between slides on mobile devices - I used React Swipeable library to implement this feature.

As always, I'll be grateful for any feedback.

Thanks & Happy Coding! 🎃

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • solitary_coder•1,000
    @kabir-afk
    Posted over 1 year ago

    Was working on the same challenge , would be helpful to compare our codes when I'm done

  • Rafael Sequeira Sandoval•270
    @RafaelSS427
    Posted over 1 year ago

    Hi Better5afe, I really enjoyed your work! I would like to share with you 2 possible improvements you could implement.

    1. It would be great to pause the animation of your image carousel when the user's cursor is over it.
    2. Every time the user changes image, you could reset the time it takes for the carousel to go to the next image, this will avoid abrupt jumps between images.

    As you can see these are improvements related to the user experience. I hope my observations are helpful! :D

  • Marvellous Obatale•520
    @MARVELGARR
    Posted over 1 year ago

    nice, only there is a small responsive error in mobile view... i need to go and update min cause i left out some features like hover and favicon

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

Oops! 😬

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

Log in with GitHub