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

Responsive product card using CSS Grid and Flexbox

Adnan Cezar Zanbouah•30
@aczanbouah
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 tackling responsive design for the first time and being able to refresh my CSS skills. I think the way I approached the project was good enough but I would try to find better ways to optimize the CSS and organizing the HTML.

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

I've encountered many challenges but the greatest one was using CSS Grid instead of Flexbox to arrange the main layout. Selecting the grid area is a bit confusing to me. I eventually managed to get it working through trial and error.

Another big challenge I've encountered was changing the image from the mobile version to the desktop one. This is where I found out about the <picture> element and the srcset attribute which helped me solved it.

The last challenge worth mentioning was solving the problems caused by the breakpoint of going from one column to two columns and figuring out a way to stop the img container from shrinking when resizing towards the breakpoint. I eventually solved it by setting a min-width on the container but I'm pretty sure there might be better solutions out there.

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

I'd like to know in which scenarios I should be using pixels instead of other units or when I should be using other attributes such as min/max width/height in relation to responsiveness.

Also another area I'd like feedback on is the way I've structured the HTML. More specifically, are there other semantic elements I could've used and is the way I've chosen which element should have a class/id right? Besides that, are the CSS selectors I've used the right way to do it?

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 Adnan Cezar Zanbouah'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

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.