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

Responsive Product Preview Card using SASS

sass/scss
Lauren Delmar•100
@lrdelmar
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 am really pleased with the responsiveness using grid and media queries for the layout. My first time applying SASS to a project so it took me much longer to complete this. Also first time doing a mobile-first design so having to think backwards was challenging. I was going to use a pseudo element (::after) for the "old price" but I realised this was not good for accessibility.

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

I had difficulties getting my head around using breakpoints, using clamp() for responsive fonts and width: min() for responsive layout. Did a lot of trial and error before finding the sweet spots. Also the architecture of SASS was a bit confusing at first, knowing how to structure the folders. I can see now how this makes it easier to work on a project.

Also getting the image to change from mobile to desktop took me a while, looking at StackOverflow I realised I could include both images in the HTML, using display: none or display: block at the right breakpoints allowed me to hide and show the relevant image.

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

I could probably structure the SASS folders better next time, it's new to me so it's a learning process at this point. Any feedback on whether I could have done anything differently to make the code simpler would be appreciated.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Adriano•42,890
    @AdrianoEscarabote
    Posted 9 months ago

    Hi Lauren Delmar, how are you doing? I really loved the outcome of your project, but I have a few suggestions that I think might be helpful:

    Use the THE PICTURE TAG that is a shortcut to deal with the multiple images in this challenge. So you can use the <picture> tag instead of importing this as an <img> or using a div with background-image. Use it to place the images and make the change between mobile and desktop, instead of using a div or img and set the change in the css with display: none with the tag picture is more practical and easy. Note that for SEO / search engine reasons isn’t a better practice import this product image with CSS since this will make it harder to the image. Manage both images inside the <picture> tag and use the html to code to set when the images should change setting the device max-width depending of the device desktop + mobile.

    Check the link for the official documentation for <picture> in W3 SCHOOLS: https://www.w3schools.com/tags/tag_picture.asp

    See the example below:

    <picture>
      <source media="(max-width:650px)" srcset="./images/image-product-mobile.jpg">
      <img src="./images/image-product-desktop.jpg" alt="Gabrielle Parfum" style="width:auto;">
    </picture>
    

    The rest is excellent.

    I hope you find it useful. 👍

    Marked as helpful
  • Dylan Heslop•2,440
    @dylan-dot-c
    Posted 9 months ago

    Well done! This is a great solution.

    One thing you can do differently is to use the picture tag/element to easily switch between pictures by using the media attribute to specify what ranges this img should show on. I suggest you search it up and see how it can be used.

    Also for item-pricing you can use flex instead of grid just for less code and complexity.

    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

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