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

fourCardFeature_figmaChallenge

P
Anjelica•160
@Anjie-MF
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?

Honestly? I’m proud that I didn’t give up. There were so many points this week where I wanted to scrap the whole thing and switch to Flexbox (which would’ve been way easier). But I stuck with CSS Grid even when it made me want to throw my laptop out the window.

I’m also proud that I learned to trust the grid system. Once I stopped trying to force it and started thinking in rows, columns, and spans, everything started to make more sense. That mindset shift is something I’ll carry into future projects.I’d definitely start with a 12-column grid right away. I originally used 5 columns without knowing why, which just made layout math harder. I also over-nested elements (like wrapping cards inside .content-wrapper), which caused a ton of alignment issues. Next time, I’ll start simpler and avoid adding complexity unless it’s needed.

And I’d double-check my syntax early—I lost hours to one space in 1 fr (repeat(5, 1 fr) instead of 1fr). Brutal.

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

Broken layouts with no clear error – I realized that invalid CSS (like repeat(5)) doesn’t throw errors, it just silently fails. I had to dig into DevTools to understand what was going on under the hood.

Misaligned card widths – The cards weren’t lining up because of mixed grid contexts. Removing the nested .content-wrapper and placing all cards in one unified 12-column grid finally solved it.

Column stretching – I learned how even small content differences can stretch grid tracks. I used min-width: 0, removed floats, and inspected grid overlays.

Temptation to quit – This was real. But I asked for help (including Stack Overflow, LinkedIn, and Discord), and that made all the difference.

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

The mobile layout! I think I got the @media (max-width: 600px) logic right, and I’m stacking cards the way I want, but I’d love a fresh set of eyes to double-check that:

My grid-column values are clear and consistent

I’m not overcomplicating the stacking order

My padding/margins are responsive-friendly

If anyone spots any refactor opportunities or smarter ways to handle breakpoints, I’d love to hear them!

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