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

Four card feature section with CSS grid and clamp() function

Ryan Hardy•140
@ryyHardy
A solution to the Four card feature section 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 am proud of the HTML because I got it done very fast despite not taking on a frontend mentor challenge in a few months. I am also happy with the decision to go mobile-first on the design and getting the media query done. I think the final result looks really close to the design files, too.

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

My knowledge of CSS grid is very much a work-in-progress. It took me a while to figure out how to give the grid that "staggered" layout. Also, I wanted to use the clamp() function more, and it worked eventually, but I struggled a lot with finding the right units/values to use. Like always, units are hard.

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

In my media query, I had an issue where the font would appear too large just after the transition, before becoming normal again as the width increased. I heard it's a common struggle to handle font sizes during a media query or layout transition, so any advice is welcome.

Also, I would love to get better at using the clamp() function. I had a hard time with using a mix of different units for the parameters and getting an intuition for how the function works.

Finally, feel free to give feedback in any area you see fit.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Cristian Alexa•120
    @CristianAlexa
    Posted 4 months ago

    Hi,

    Looks very good. Great job.

    You can also limit the width of the sub-title - you can use max-width for it. You can also use <article> instead of <div> for the .gallery-card elements.

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.

Oops! 😬

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

Log in with GitHub