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

Four Card Feature Section

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

Solution retrospective


Finally! I finished this challenge. I really got learnings from using grid layout because the design was kinda needed to be coded using it. I want to know more about css grid layout and tips and tricks. Maybe you can put some in a comment? Thank you!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Lucas 👾•104,160
    @correlucas
    Posted almost 3 years ago

    Hello Fahatmah, congratulations for your challenge solution!

    You did a really good work, wrapping all the content and setting the media queries changing the font-sizes on mobile.

    I look your live site and I've some tips for you:

    1. The content wrapped inside the main container isn't proper centered because your add an unnecessary margin-top inside of the .four_card_container --> margin-top: 4.5rem;, remove that and your container will be centered.

    .four_card_container { margin-top: 4.5rem; }

    1. The cards box-shadow has too much opacity, you can play with opacity and blur values to create a soft box-shadow try something around box-shadow: 40px 60px 50px -47px rgb(26 33 45 / 50%);

    2. The colored-bar in each card doesn't need a border-radius, if you look the design files you'll see that the colored bar is flat. You can create these bar using an element like an <span> and use the property overflow: hidden; to force this element stay inside the card.

    3. About flexbox and grid you can learn a lots about them reading the documentation in W3 Schools, but if you want to learn it with the practice, try these games, is a really cool way to see many grid/flex properties:

    • Flexboxfroggy : https://flexboxfroggy.com/
    • CSS Grid Garden: https://cssgridgarden.com/

    I hope it help you in some way, then say me what you think about. Congrats.

    Marked as helpful
  • Divine Obeten•2,415
    @Deevyn9
    Posted almost 3 years ago

    Hi Fahatmah, great solution here, you should add a little more margin to the top of the cards container.

    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

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