Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 4 years ago

four-card-feature-section

KAKANAKOU Miguel Stephane•100
@MiguelSteph
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

  • Grace•32,130
    @grace-snow
    Posted over 4 years ago

    Hi

    Well done on completing the challenge. I have some suggestions for and some questions about your approach if that's OK...

    • first, it's a shame you've not used css grid for this. The challenge is a 2 dimensional layout that's perfect for grid. Flexbox is suited to 1 dimensional layouts
    • on mobile portrait all the cards are off center for me. This is because you're using percentage widths and a min-width on the card. That min-width is wider than 90% on my phone. Width 100% and only a max width on the card would be better.
    • following on from that, you may find you have more control over styles of you use padding on blocks/elements wrapping other items instead of percentage widths, which can vary greatly depending on context.
    • its best to use Em or another relative unit for letter spacing or text will become unreadable when zoomed
    • why are you positioning the card wrapper absolutely?
    • why is there an important in the css?
    • in html you've jumped a heading level. Your h4s should be h3s.

    Overall the rest of the solution looks close to the design. I hope these ideas help you for this or future challenges

  • KAKANAKOU Miguel Stephane•100
    @MiguelSteph
    Posted over 4 years ago

    Hi @Grace-snow

    Thank you again for your useful suggestions. I have apply them in this commit https://github.com/MiguelSteph/four-card-feature-section/commit/5dd0f8860e0ddd7d5535499707f8e1e81dd258e8

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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