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

Product preview card solution

Art0fMind•90
@art0fmind
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 especially proud of the quality of the responsive design I implemented. The "Product preview card" component adapts perfectly to both small and large screens, with polished hover states that enhance the user experience.

What I’d do differently next time Next time, I’d spend more time organizing my CSS code using a more modular structure with utility classes or even a solution like SASS or Tailwind, to improve clarity and reusability.

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

One major challenge was vertically centering the content in the mobile version without breaking the desktop structure. I had to tweak several flexbox properties and play with conditional margin and padding in media queries to achieve a good layout on all devices.

Another minor challenge was handling image sizes and their behavior at different resolutions. I fixed this by using relative units (em, %, vw) and the object-fit property to keep the image clean and responsive.

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

I’d like to deepen my knowledge in accessibility (a11y), especially regarding optimal use of ARIA roles, keyboard navigation, and screen reader compatibility. Any feedback or helpful resources on this topic would be very welcome.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Art0fMind'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.