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

Responsive four card feature section with CSS Grid

Vincenzo Vitello•100
@vincenzo-vitello
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 challenges did you encounter, and how did you overcome them?

I started coding desktop first and than I had big troubles in making changes for mobile design, so I had to start the grid system from scratch thinking mobile first, and I went smoother. So I guess I'll always go mobile first from now on.

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

When I used to work as a frontend dev I only used Flexbox ignoring the existance of grid, so now I find it a bit hard to understand it because it can do so many things in so many ways that guys pls help me. Anyway, I guess I just need some more practice, but if you happen to read my code and any suggestion comes to your mind, I appreciate you hitting up. Thanks anyone, keep coding hard!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bassel || باسل•520
    @Basselfathy
    Posted 8 months ago

    Nice work, Vincenzo👏 You have done a great job so far!

    I have reviewed your code and there are two improvements you can do.

    • While you already using display:grid for the <main> on large screens, you don't need to change it to flex with column direction for small screen.

    • For the cards shadow, instead of using ::after to create it you can use box-shadow property...something like that.

    • box-shadow: 0px 15px 30px -5px #color;

    Marked as helpful
  • Dadv-a11y•550
    @Dadv-a11y
    Posted 8 months ago

    fine

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

Oops! 😬

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

Log in with GitHub