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

Responsive Product Preview Card Component with HTML,CSS

Charles•170
@charlesuzodike
A solution to the Product preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This was pretty easy to build

I have a question tho, apart from setting a flex-basis on the container to display the image and its contents side by side. Are there any other ways to set them side by side

I am open to any feedback on how I can improve and reduce unnecessary code.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Yasmine•710
    @Yasmine10
    Posted almost 2 years ago

    Hi @cacti00

    An easy way to display your image and content side by side is to use grid, you could do something like this in your .product-card class:

    display: grid; 
    grid-template-columns: repeat(2, 1fr);  /* use grid-template-columns: 1fr; for mobile view */
    

    I also saw that you're using divs with an img inside to display the image in your html. There is an html element for that actually: '<picture>'

    Here's an example of what that would look like for this project:

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

    Hope this is helpful 😊

    Marked as helpful
  • Rebecca Padgett•2,100
    @bccpadge
    Posted almost 2 years ago

    Hello @cacti00. Congratulations on completing this challenge 🎉 !!

    To answer your question you can use CSS Grid

    More info on CSS Grid📚

    CSS Tricks - CSS Grid

    Here is my solution to this challenge

    I followed Kevin Powell's YouTube tutorial on the Product Preview Component and he explains how to use the picture tag to change the images as well.

    More info on HTML Picture Tag📚

    W3Schools

    Hopes this helps you and don't hesitate to reach out to me if you have any questions ✌🏼

    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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub