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

Product preview card built with flexbox and picture element

sass/scss
P
Alexander3717•310
@Alexander3717
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 challenges did you encounter, and how did you overcome them?

Getting the image and text part of the card to be equally wide in the desktop layout was a bit counterintuitive.

I set the card’s width to 600px and the image’s to 300px, so I naturally expected the text part to be 300px wide as well — since 600 minus 300 is 300. But instead, the text part stretched to around 450px, leaving just 150px for the image.

This happened because of how Flexbox works. It looked at the natural width of the text part — basically, how wide it would be if the text could stretch freely — which turned out to be around 900px, plus the image’s 300px width. So now, Flexbox had to fit 1200px worth of content into a 600px-wide card.

To do this, it shrank both the image and the text part. That’s because by default, Flexbox allows items to shrink (with flex-shrink: 1). Both the image and the text part shrank proportionally — both halving their natural sizes. The image shrank from 300px to 150px, and the text part from 900px to 450px.

But I didn’t want the image to shrink at all. I wanted the text part to take all the shrinking instead.

The solution was to set flex-shrink: 0 on the <picture> element (not directly on the <img>, since it isn’t a flex child). That prevented the image from shrinking and left the text part to adjust its size:

.productcard {
    max-width: rem(600px);
    flex-direction: row;

    picture {
        flex-shrink: 0; // Prevented image from shrinking
    }

    &__img {
        width: rem(300px);
        height: 100%;
        border-radius: rem(8px) 0 0 rem(8px);
    }
    
    &__content {
        gap: $spacing-400;
        border-radius: 0 rem(8px) rem(8px) 0;
    }
}

HTML structure:

 <article class="productcard"> 
   <picture>
      <source srcset="images/image-product-mobile.jpg" media="(max-width: 767px)">
      <img src="images/image-product-desktop.jpg" alt="Image of product" class="productcard__img">
   </picture>
      
   <div class="productcard__content">
      Text part of the card here
   </div>
 </article>

Alternatively, I could have given the <img> a min-width of 300px, but using flex-shrink on <picture> felt cleaner and more in line with Flexbox’s intended behavior.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Alexander3717's solution.

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.