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

Responsive Product Preview Card

Ishan Ahmad•150
@ishanah09
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 how clean and responsive the layout turned out. I managed to closely match the original design from the challenge, while using semantic HTML, scalable CSS variables, and well-organized styles. The responsiveness and background image swap between desktop and mobile views were particularly satisfying to get right.

Next time, I would:

Use a mobile-first approach from the beginning to simplify responsive logic.

Consider using CSS Grid alongside Flexbox for more control over the layout structure.

Add transition effects for smoother button interactions and maybe animate the image or price reveal for a more engaging user experience.

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

Responsive Image Swap: The image wasn't appearing correctly on mobile at first. I realized this was due to inappropriate width and height settings after changing flex-direction to column. I fixed it by setting the image width to 100% and adding a specific height.

Maintaining Visual Consistency Across Viewports: It was a challenge to keep padding, font sizes, and spacing looking balanced on both small and large screens. I used relative units and media queries to fine-tune the design.

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

Accessibility: I’d like to learn more about how to make these types of cards more accessible beyond just alt text — maybe using aria attributes or better semantic markup.

Performance: Tips on optimizing asset loading (like background images) for better performance on mobile would be helpful.

Scalability: How to structure the CSS or use a CSS framework/component library without bloating the code.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Ishan Ahmad's solution.

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.