Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 years ago

E-commerce product page - React + Tailwindcss

react, tailwind-css
Fede2797•190
@Fede2797
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!, I’m Federico and this is my solution for this challenge.

Built with React and TailwindCSS.

This is the second time i use React and tailwind together and I must say I love this combination. I found the process to be very smooth and organic, easily reusing code and styling my components. I'm also very happy with the final result.

I would like some advice for styling screens around 770px. I realize those screens aren't very common, but I always find it hard to get them looking good.

Thank you 😊

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Remigiusz Czarnecki•380
    @remmji
    Posted about 2 years ago

    Hello there! 👋

    💡In regards to your question about styling screens, I would recommend avoiding hard coding font sizes. Instead, try to use one measurement for everything and stick with it. Personally, I prefer to use vw for everything to get the best results. Additionally, you can use proper media queries around 50em width to adjust the layout as needed. This will help ensure that your website looks good on screens of various sizes.

    💡One thing to note is that your project doesn't currently have a lightbox, which could be a nice addition to mimic an e-commerce site. It's not very hard to implement, and it would add a great deal of functionality to your project.

    💡Another suggestion I have is to position the cart window near the cart icon. To achieve this easily, you can give the parent element a position of relative and the cart window a position of absolute.

    I hope these tips will help you tune up your project ;)

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub