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

four card component using css grid

Cipher126•120
@Cipher126
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Gabriel Rodriguez Perez•160
    @glrodriperez98
    Posted 3 months ago

    @Cipher126,

    I checked out your Four Card Feature project and just wanted to say...great job overall! Your layout is super clean, your use of :root variables makes the CSS really organized, and everything feels polished and accurate to the design.

    Here are a few things I really liked:

    Grid Layout: Your use of CSS Grid to position the cards was awesome. I liked how you used specific grid-column and grid-row placements to arrange them uniquely — it mirrors the original design well!

    Card Styling: Each card looks visually distinct with the top colored border using the ::before pseudo-element - something I have yet to dive into so nice job!

    Responsiveness: I appreciated that you included media queries to make it mobile-friendly by switching to a column layout using Flexbox. That really helps the user experience on smaller screens.

    A few small suggestions:

    On mobile, the .card styles inside the media query have a grid-template-columns line that doesn’t apply to Flexbox — you might be able to clean that up.

    You could consider using grid-template-areas to make your layout even more readable and maintainable, especially if you plan to iterate on the design more later.

    But honestly, you're super close to pixel-perfect! You clearly put in a lot of effort...well done!

    Kind regards, G

    Marked as helpful

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