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

Responsive Product Preview Card using Flexbox and Media Queries

Selasi•100
@Sussana7
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'm most proud of achieving a clean, responsive layout that adapts well to different screen sizes. I also kept my CSS organized and avoided using unnecessary code. Next time, I would focus more on accessibility and performance optimization, such as using more semantic tags and reducing image file size.

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

One of the main challenges was getting the layout to work correctly on both mobile and desktop screens. I overcame this by starting with a mobile-first approach and using media queries to adjust the layout for larger screens. Another challenge was ensuring that the text and button spacing matched the design closely, which I resolved by adjusting paddings and margins carefully.

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

I need help with the image not displaying on the live site. It shows up locally, but when I deploy it, the product image does not appear. I'm not sure if it's a file path issue or something else. Any suggestions to fix this would be appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marzia Jalili•9,250
    @MarziaJalili
    Posted 3 months ago

    Gorgeous! 👑

    Here's the fix:

    ✅ The reason of your image not being rendered correctly is because if the wrong path set for the src.

    ✅ This path src="images/image-product-desktop.jpg says: go through the images folder and find image-product-desktop.jpg. However, we haven't set the image inside a folder 😳.

    ✅ To fix it you can either create a folder named images and move all the images there or simply remove images/ before the name of the file.

    This will definitely click!

    😎😎😎

  • Amir Shamim•90
    @AmirShamim
    Posted 3 months ago

    You have set the wrong path for your image in the repository. Just remove "images/" from src <img src="images/image-product-desktop.jpg" alt="Gabrielle Essence Eau De Parfum bottle" /> I think you uploaded all these files by drag and drop, not by git cmd.

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