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

Product-preview-card using tailwindcss and flexbox

tailwind-css
Rafael Ibarra•120
@rafbar2000rr
A solution to the Product preview card component 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 starting to understand responsive design, next time I will try to understand more and more each step during the coding process.

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

When I resized the window to check the change in the layout from mobile to desktop, I saw no changes. Then, I realized that it was not necessary to write exactly 375px in the tailwind.config.js file. I could simply write a greater number, so finally it worked.

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

I would like to know if there is another way in Vercel to select the folders, because I use to move the images from the images folder to the src folder, otherwise Vercel cannot read the images. I don't know if what I do is really necessary or there is a better way to do it.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Huy Phan•3,430
    @huyphan2210
    Posted 9 months ago

    Hi, @rafbar2000rr I took a look at your solution and I have some thoughts:

    • Regarding your question about Vercel, I don’t think the issue is that Vercel can’t read the images from the images folder. It’s more likely that the src path in your img tag was incorrect. Try placing the images back into the images folder and update the src attribute. For example, instead of src="./image-product-mobile.jpg", use src="./images/image-product-mobile.jpg".
    • If that doesn’t resolve the issue, another option is to create a public folder at the same level as your src folder. Move your images folder into public, and you should then be able to reference the images without including public in the path. For example, change the src to src="images/image-product-mobile.jpg". Vercel (and many other hosting platforms) recognizes the public folder automatically.
    • Also, which IDE are you using? A good IDE should help by suggesting the correct URI when you’re writing the src attribute, which can prevent mistakes like this.

    Let me know if you have any questions. Hope this helps!

    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