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

Responive 4-card-profile solution using CSS flex.

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

Solution retrospective


Let me know If I did anything wrong. I think there is a problem with positioning in mobile version.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Pawn•320
    @CryptoPawn
    Posted over 3 years ago

    Hey. Great work with completing this challenge! I love the use of rem units on the text styling and is something I'm going to start using as well. I'm going to give a bit of feedback on the code which. I will also explain the problem you are having with the mobile version's positioning.

    • The text elements inside the header are wrapped into divs, applying the wrappers' CSS to their respective "content" would give the same result.

    • Each section's header has an unique class. Same result is achievable by using section h3 { ... }. This makes the code cleaner and one would not have to type them all out in the styling.

    • The sections have their margin hard-coded, which can be tedious further down the line if one would want to add more cards. Making three flex columns containing the cards would offer a more simple and effective way of displaying the cards.

    • If you go to inspect the <main> and <header> elements on the mobile version, you will see that these elements' has a margin extending out to the left and/or top. Removing these margins will solve your positioning problem.

    Hope all of this comes in handy. Let me know if you would like to explain anything further.

    Again, good job with this challenge, the website looks great and as intended! I'm excited to see more challenge solutions from you in the future!

    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