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

GRID / Responsive - Four card feature section

Fidget836•20
@Fidget836
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I tried a solution with display: GRID, I would like to have your opinion if GRID was for you the best option or another solution would have simplified things and is my GRID semantically is good? Last question, on my sections is it better to put an ID or a class? Thank you, Have a good day !

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bagas Defandi•170
    @bagas-defandi
    Posted about 3 years ago

    Hi Fidget!

    congrats on completing this challenge!

    to fix the Accessibility issues you can wrap <section id="secondeSection"> with <main> tag, and I think <section id="firstSection"> should be <header> tag.

    for styling things don't use ID because ID have a high specificity, I always use class or element it self to styling html.

    I also did this challenge with Grid I use grid-template-areas to make it responsive, you can see my solution here

    I hope it helps you :)

    Marked as helpful
  • Lucas 👾•104,160
    @correlucas
    Posted about 3 years ago

    Hello Fidget, congratulations for your solution!

    I did this same challenge and I've used Grid because I consider that was better to manage the columns, but I saw some person that finish this challenge using Flexbox, I think if you manage this challenge using flexbox you'll need to have much more div to hold the container.

    About your question about id and classes, I think id is stronger that classes when selecting properties/elements, but you can do everything with only classes in a simple page like this challenge, is better you use id for challenges where you'll use forms and Javascript.

    If you want to see how I built the same challenge heres my solution: https://www.frontendmentor.io/solutions/4-card-feature-section-vanilla-css-custom-design-glassmorphism-35MDUfOBdt`

    I hope it helps you, congrats for the challenge!

    Marked as helpful
  • Fidget836•20
    @Fidget836
    Posted about 3 years ago

    https://fidget836.github.io/ for see the good version. It shows here a responsive version so the result is not the same.

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

Oops! 😬

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

Log in with GitHub