Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

Responsive preview card - media queries + clamp()

sass/scss, vite
P
Michael•180
@Networksentinel
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 pretty proud of how I handled the layout changes for different screen sizes. It wasn’t just a simple clamp() fix — the design needed the component to start small on phones, get bigger by tablet size, then shrink a bit, and finally grow again on bigger screens.

It was kind of tricky, but I made it work by mixing @media queries with clamp(). The layout feels smooth and responsive, and it really matches the Figma design closely.

Next time I will commit more often in Git, and be more intentional with it. Like, really think about what each change is doing to the layout or visuals, and pick a commit message/label that fits.

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

Like I said before, making the layout work well on all screen sizes was tricky.

Another thing that bugged me was this huge gap showing up under the <footer>. I was honestly almost frustrated trying to figure out what was going on.

Turns out, it’s just how browsers behave when the page content is smaller than the screen height — I knew this already, but totally blanked on it with everything else going on. After like two hours of debugging and comparing with my old projects, I finally cracked it.

Funny how sometimes the simplest stuff ends up being the hardest to remember!🤦‍♂️

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

If anyone has tips on handling responsiveness more effectively, I’m all ears! Same goes for my mixins — if you see anything I could improve or clean up, let me know. Any trick or suggestion is totally welcome and appreciated 🙌

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • nerdynischal•170
    @nerdynischal
    Posted about 1 month ago

    Looks identical and really well done to the details.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub