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

Media queries for responsive design, and css variables.

kevin•90
@kevcoder247
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 found it difficult to figure out how to display two images, or how to have both desktop and mobile images in the same html file.

I'm unsure about how I wrote my css in order to position things, feels like I can write much better css, but I learned a lot which was great.

Would like to know where or how to store or how to work with different image sizes when going from desktop to mobile.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dusan Brankov•860
    @dusan-b
    Posted over 2 years ago

    Hello Kevin,

    to allow the browser to choose the appropriate image regarding the screen size, you should use the <picture> element.

    You could do something like this:

    <picture>
      <source srcset="./img/image-mobile.jpg" media="(max-width: 400px)" type="image/jpeg">
      <img src="./img/image-desktop.jpg" alt=" Some alternative text">
    </picture>
    

    This way you are saying to the browser to load the smaller image for devices that are up to 400px wide, and otherwise to load the bigger image. You can also add more image versions by adding multiple <source> elements.

    MDN has a great article about it, to get started:

    <picture>: The Picture element

    Hope this helps. Happy coding!

    Marked as helpful
  • Salmane•220
    @salmaane
    Posted over 2 years ago

    Hi Kevin! Good job your project is awesome.

    For your question about manipulating images when moving from desktop to mobile or vice-versa, There is many methods but I used to do this one: you have to add the two images (desktop & mobile) to your html code and set the mobile image display property to hidden . and when you move from desktop to mobile by media queries you have to set its display property to block (or inline) and for desktop image set display property to hidden. By this you will be able to change between desktop and mobile images.

    I wish this will help you!

    Marked as helpful
  • suhayb jirde•1,110
    @suhaybjirde
    Posted over 2 years ago

    well done

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

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