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

Responsive product card component using HTML & CSS

P
Kyle Mulqueen•400
@kmulqueen
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'm most proud of successfully implementing responsive images using the <picture> element to serve different images at different breakpoints. This was particularly satisfying because I tackled the challenge of having a wider mobile image (686px) than desktop image (600px), which made traditional srcset approaches less reliable.

Next time, I would start with a more semantic HTML structure from the beginning. I had to restructure elements later to improve accessibility and semantic meaning, which would have been easier to implement from the start.

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

The main challenge was controlling which image version displayed at different breakpoints, especially since my mobile image was unexpectedly wider than my desktop image. The srcset and sizes attributes weren't behaving as expected.

I overcame this by:

  1. Learning about the <picture> element which allowed explicit control through media queries
  2. Using DevTools to inspect the behavior at different breakpoints
  3. Seeking assistance to understand why my original approach wasn't working

Another challenge was getting equal-width columns in the desktop layout, which I resolved by applying width: 50% to ensure consistent rendering.

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

I'd appreciate guidance on:

  1. Typography scaling - my use of clamp() for responsive font sizing led to compounding effects with my CSS custom properties
  2. Best practices for SVG implementation - particularly controlling color and size efficiently
  3. More accessible markup patterns for product cards - ensuring my component follows best practices for screen readers and keyboard navigation
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Devesh Soni•100
    @DeveshSoni973
    Posted 3 months ago

    That is one fine site, I mean almost perfect imo, one thing tho, I saw that on my pc, I had to use the scrollbar to get to the bottom of the webui, and that some portion of the webpage, I gotta scroll. I do not think it was intended. Maybe adjusting the elements wrt the max-width from the window? (get it dynamically from browser :)))

    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