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

grid-basic-learn-to-handle-column-responve

react
IRON Michael•180
@Iron-Michael
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 think i can use fonts better than never before

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

i struggle a little bit about grid but use my ai my copilot and then i can esily pass this

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

what do you think do you think do you have easy way to handle grid and make code cleaner than my code??

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    fringe4life•160
    @fringe4life
    Posted 5 months ago

    Hi, this site suffers from what is called divitis. There is clearly a header, which is the static text at the top and then a main area which is the four cards.

    Yes grid can be much simpler then this. My solutuion was to have 6 columns at tablet sizes and 4 rows at larger sizes and 3 columns. Feel free to use dev tools on my live site: https://four-cards-frontend-mentor-typescript.netlify.app/.

    I would really recommend spending some time learning grid more by going back in the path and looking at some of the resources they provided in the learning part of this path as grid is basically necessary as a CSS tool nowadays.

    Your header text sizing is also clearly off and the margin above it is supposed to change at different viewports.

    I really hope you try this challenge again after you have spent some more time looking at css grid.

    Congrats on deploying a build version of react!

    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