Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

CSS Responsive design

cloudpc7•180
@cloudpc7
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?

What I did was write up the code for the mobile design first. I would definitely make sure that I am correctly making all designs I do more responsive

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

I still have concerns about my max and min widths when creating the mobile desing

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

I would like assistance with the @media queries and like to know if I am providing the max-width to the container as well as the buttons.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ortaly•1,190
    @ortalyarts
    Posted over 1 year ago

    Hello @cloudpc7, Good job so far!

    Image issue - the perfume image is distorted. For this are two reasons

    1. You used mobile image for desktop screen. For this project we were provided with two images for desktop and for mobile designs. To handle this you can use <picture> tag. It allows you to make madia queries. Just example:
    <picture>
    	<source srcset=”images/40under40_full.jpg”
    		media=”(min-width: 40em)”>
    	<source srcset=”images/40under40_medium.jpg”
    		media=”(min-width: 20em)”>
    <img src=”images/40under40_small.jpg” alt=””>
    </picture>
    

    Read more here

    1. It is better to set a max-width for an image container, while for the image itself set max-width: 100%; height: auto; . This makes your image responsive and preserves its ratio.

    For designs like this I prefer to use grid. Try setting the main.container to display: grid; grid-template-columns: 1fr 1fr; for desktop. This will provide you two equal columns for image and for div.content.

    As for your question about the @media queries: You just check when your design starts to be too squeezed on narrow screens and set a media query for that point. For example in this project you could set a starting point for desktop design like this: @media screen and (min-width:40rem) { ... } and insert the grid-template-columns: 1fr 1fr for your main.container like explained above.

    I hope you find this helpful! Cheers 😊

    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