Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 19 days ago

Responsive product card component

Udara Lakshitha•50
@UL-code
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 implementing a fully responsive design using the <picture> element and mobile-first approach. The way I handled different image versions for mobile and desktop screens worked really well.

For next time, I would:

  • Add more interactive animations to the button
  • Use CSS Grid alongside Flexbox for more complex layouts
  • Write more organized CSS using BEM naming
What challenges did you encounter, and how did you overcome them?

My main challenges were:

  1. Image Responsiveness

    • Problem: Making images look good on both mobile and desktop
    • Solution: Learned about the <picture> element and used different image files for each screen size
  2. Consistent Sizing

    • Problem: Getting consistent measurements across the design
    • Solution: Used rem units with html { font-size: 62.5% } to make calculations easier
  3. Button Styling

    • Problem: Making the button match the design exactly
    • Solution: Used CSS custom properties for colors and added proper hover/active states
What specific areas of your project would you like help with?

I would appreciate feedback on:

  1. CSS Organization

    • Is my CSS structure clean and maintainable?
    • How can I better organize my custom properties?
  2. Accessibility

    • Are my HTML elements semantic enough?
    • How can I improve keyboard navigation?
  3. Performance

    • Are there better ways to handle the responsive images?
    • Could my CSS be more optimized?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Andrey•4,060
    @dar-ju
    Posted 19 days ago

    Hi, Udara Lakshitha!

    Great solution for the first work in FM!

    Semantics are correct.

    I could add about CSS - just don't use .price .old-price{ nesting, you already have the .old-price class, use .old-price{

    Keyboard accessibility is not important here, there is only one active element here, this is a button and focus on it works.

    For background and decorative images, leave alt empty, in the example with the basket icon, search engines and readers do not need this information, just do alt=""

    Otherwise everything is great, keep it up!

    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