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

Product Preview Card Component built with SCSS and Flexbox

sass/scss
P
Shakira Reid - Thomas•200
@KaeTheDev
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 proud of getting the responsiveness just right, ensuring that the design closely matches the final vision. In my last project, the Recipe Page, I struggled with layout and responsiveness—I got everything looking right, but the structure didn’t quite work as intended. With this project, I’ve learned valuable lessons that I plan to apply when I revisit and improve the Recipe Page project.

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

I struggled with deciding whether to approach the design with a mobile-first or desktop-first strategy, as I wanted to avoid the same issues I faced in my last project. At first, getting the mobile layout right without affecting the desktop layout was a challenge. However, I worked through it by carefully adjusting breakpoints and testing the responsiveness at different screen sizes.

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

I took a different approach to handling responsiveness this time, and while I understand that every project requires a unique strategy, I’d love feedback on whether my approach makes sense. I’d also like to know if the techniques I used could be applied effectively in future projects.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Osvaldo Valdivia•230
    @progValji
    Posted 6 months ago

    Hi, I've seen your code and it seems very good. However, I would like to share some of my points of view: The handling of the source tag is quite good, personally I don't use that tag, I only do it with CSS and the help of media-queries. You can do the following: Use <picture> for semantic images that require technical adaptation (formats, density, art direction). Use CSS Media Queries for backgrounds or decorative elements where accessibility is not critical. In modern projects, combine both: <picture> for content and CSS for layout. My last recommendation is that you use BEM, this helps you reuse classes and make your project maintainable in the future.

    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