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

Responsive Four card feature using CSS Grid

vite, sass/scss
P
Michael•180
@Networksentinel
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 finally got to use CSS Grid for real in this project—and wow, it's powerful! I’m still wrapping my head around everything it can do, but even with what I know so far, it made laying things out so much easier.

While building the layout, I experimented with both:

  • grid-template-columns / grid-template-rows
  • grid-template-areas

Both worked really well, but I ended up using the latter:

.feature__nav {
    display: grid;
    gap: $space-lg;

    @media (min-width: 768px) {
        grid-template-areas: 
        "top top"
        "mid1 mid2"
        "bottom bottom";
    }
    @media (min-width: 1440px) {
        grid-template-areas: 
        "left mid1 right"
        "left mid2 right";
    }
}
What challenges did you encounter, and how did you overcome them?

Honestly, this was the first challenge where everything just kind of made sense. I didn’t really struggle or get stuck—I was able to keep moving forward without overthinking things. It all felt really smooth.

The main challenge was figuring out how to use CSS Grid properly—it was my first time really using it in a meaningful way. I used @media queries to handle the layout switch, but I know there's so much more CSS Grid can do. I'm excited to keep learning and see what it's really capable of.

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

I’m really curious if there’s a better way to switch between different Grid layouts without relying on @media queries. Like with Flexbox, I can use flex-wrap: wrap; to let items drop to a new row and kind of change the layout automatically.

  • Is there something similar I can do with CSS Grid?
  • And would that actually make sense for this particular challenge?

Any tips, tricks, or advice would be super appreciated!

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 Michael'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.