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

Responsive Product reviewer card

Roxana Valeria Solernou•30
@RoxxVS
A solution to the Product preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I'm having trouble getting a truly responsive background-image. Any tips for me?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Fortune Iyoha•310
    @fortuneiyoha
    Posted almost 2 years ago

    Congratulations on completing the challenge! 🎉

    Picture Tag 📸:

    • Noticed you're using media queries to swap images? Consider the <picture> tag, perfect for responsive images and art direction.
    • Example:
      <picture>
        <source media="(min-width: 900px)" srcset="large-image.jpg">
        <source media="(min-width: 768px)" srcset="small-image.jpg">
        <img src="fallback-image.jpg" alt="Example image">
      </picture>
    
    • It allows different images for various screens without CSS, improving load times by serving optimized images.

    • Questions? Check my submission or reach out anytime.

    • For more information, you can Learn More about the <picture> element on W3Schools.

    Great job! 😄

    Happy coding!

    Marked as helpful
  • Nelson Pascual•130
    @NelPascual
    Posted almost 2 years ago

    Hello Roxana. I hope you are feeling well. According to your concern about how to handle responsive images, looking at your code I understand that you started the project from the desktop perspective, since the image you call at first is the image-product-desktop.jpg, based on this I think that things are generated that you do not expect, you should change it to image-product-mobile.jpg; then in the media queries you use the desktop, in my case the image that corresponds to mobile I use it up to a maximum of 640px, from then on I change to the desktop.

    A tool that I use to see the responsive details, at the time of developing the code is the app called ResponsevelyApp, I do not know if you know it?

    I hope I didn't confuse you, or misunderstand your concern, anyway, if you have any questions we are at your service.

    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 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