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

Responsive product preview card, using flexbox

Adriana•60
@AdrianaMagdalena
A solution to the Product preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


My biggest issue was with setting background-image property. I'm only used to putting <img> tag in html and providing source to the picture there, but in this project I felt I had to create a container for the picture and use css background-image property. I don't have a proper understanding of this method and all the background-size, and background-repeat properties, so my design kept being wonky for a long time without me understanding why. Even when I succeeded to put it toghether properly, I'm still not sure if my method is the best solution. I'd be extrememly grateful for feedback on it.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rino•340
    @Rhinozer0s
    Posted almost 2 years ago

    Hello Adriana ✌️

    I have a recommendation to solve your issue with the background.

    For responsiveness it is usual to use the Picture-element

    • The <picture> element contains two tags: one or more <source> tags and one <img> tag.

    • in the <source> tag you can define your media queries

    In your case it could look like this:

    <picture>
    <source media="(max-width:600px)" srcset="images/image-product-mobile.jpg">
    <source media="(min-width:600px)" srcset="images/image-product-desktop.jpg">
    <img src="images/image-product-desktop.jpg" alt="Product">
    </picture>
    

    I hope you find this helpful 😄 Above all, the solution you submitted is great !

    Happy coding!

    Marked as helpful
  • Tushar Biswas•4,060
    @itush
    Posted almost 2 years ago

    Congratulations on completing the challenge! 🎉

    Welcome to the platform!

    Yes, for projects like this we need to figure out a way to toggle images. There are multiple ways to do that and using background-image property is perfectly fine in this situation. You might want to play with this approach for couple of projects first... and once you are comfortable with the approach and using background shorthand etc. then you may explore other methods.

    Your final solution looks nice. However I'd like highlight the following to make it nicer :)

    • Looks like there is a typo in the body declaration block height: 100dvh;

    • .wrapper may need some top margin for mobile-view.

    • Try using more html semantic elements, and avoid divs as much as possible.

    Feel free to checkout my live site and project code I've used html semantics and background shorthand.

    Once again you have done a wonderful job.

    And I look forward to see cool projects from you in the future🚀

    Keep at it...💻 Happy hacking!

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

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