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

Using css media-queries to change content based on screen size.

Amhed Hussien•390
@Eng-Ahmed-Hussien
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 the responsive design turned out, especially the use of CSS media queries to switch images dynamically for different screen sizes. This helped maintain a clean and structured layout across devices.

Next time, I would explore using CSS Grid instead of Flexbox to manage the layout, which might offer even more flexibility. I’d also consider adding CSS transitions to make hover effects smoother and enhance the user experience.

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

One challenge was ensuring that the image swapped correctly on smaller screens using content: url(). Initially, the mobile image didn’t load properly, but I resolved this by making sure the file paths were correct and using media queries effectively.

Another issue was managing text wrapping and spacing in the mobile view. Some elements felt cramped, so I adjusted padding and font sizes dynamically to improve readability.

By testing across different devices and tweaking the styles, I ensured the design looked great at all breakpoints.

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

Responsive Design:

Are there better ways to manage image swapping for different screen sizes? Should I use picture elements instead of content: url() for better support? Accessibility & Usability:

Are there any ARIA attributes I should add to improve accessibility? Should I make the card’s buttons and links more distinguishable for better user interaction? Code Optimization:

Are there any CSS best practices I might have missed? Would using CSS variables help make styles more scalable and maintainable?

I appreciate any feedback that can help me improve my approach! 🚀

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 Amhed Hussien'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.