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

Responsive Product Preview Card Using Flexbox and Media Queries

Linda Jensen•80
@lindajensen
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 think I'm most proud of the fact that I figured out how to use two different pictures using the picture element. Or no, I'm probably most proud of the fact that I tried a mobile-first workflow and did great. It was like something just clicked and I felt like i temporarily knew what I was doing and where to start and how to move forward. It was just an amazing feeling. Especially since I've been in a place where I've just felt like I don't understand a thing and I'll never be good enough and well you know...

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

The first challenge was actually how to use two different pictures. I think I tried a gazillion different ways before even getting it to work. It was probably not as complicated as I made it out to be, but I just couldn't get it working. I spent a couple of hours on it and ended up using the picture element. Me having set a max-with on the card complicated things a bit but when I increased the max-width on the card in the media query it worked just fine.

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

I'd like to know if using the picture element was the best way to go or if there are other (more suitable) solutions? How did you do it?

And then just general feedback I guess, anything you can tell me that can help me develop is much appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Account deletedPosted over 1 year ago

    Thinks I noticed:

    • You should have used fontweight on the button element to make it bold.
    • I think the margin between the image and content could be better.

    Great work.

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