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

Four card Feature section

Keagan Dickinson•160
@PhisherFTW
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Nice CSS challenge, if anyone has any recommendations or tips, I would love any feedback I am sure there was a better way to position the Karma section rather than using absolute, so if you managed it with grid or a different method please let me know.

Thanks

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Leo•440
    @Souicia
    Posted about 3 years ago

    Hello Keagan,

    First of all, congratulation on completing the challenge. I think a better solution rather than using position absolute, mainly without using a relative container, it could lead to problems on a bigger site, would be to use flexbox instead. For this challenge, I would suspect a better way would be: making a main div around all four boxes and giving the attributes of display: flex; flex-direction: row; justify-content: center; align-items: center;. Then for the two middle boxes, you enclose them within another div and this div you make it as flex with flex-direction: column;

    So from your source code it would look like: /use the main tag for your main body/

    <header class="top box">rest of code... </header> <main class="main-container"> (flex-direction: row) <div class="supervisor box"<div> <div class="two-middle-boxes"> (flex-direction: column) <div class="team-builder box">rest of code...</div> <div class="karma box">rest of code</div> </div> <div class="calculator box">rest of code</div> </div>

    I hope you understand my point. If you don't, feel free to ask me. Little bonus: In your media query class "line" use align-items center for so that all the boxes are centered when resizing the window.

    Marked as helpful
  • Marzouq Adebayo•90
    @AdebayoMarzouq
    Posted about 3 years ago

    Hi Keagan. Congratulations on completing the challenge.

    A better solution would be picturing the entire section as a grid with 3 columns. The first and third columns would have just one centered card while the second column would contain two cards. i.e 1fr 1fr 1fr then use flexbox or grid in each column to place the cards inside each of the columns

    I hope this helps

  • Manoj Kumar Singh•970
    @dev-mksingh
    Posted about 3 years ago

    Hey Keagen, I just completed this challenge with the help of Flexbox and Grid. It might help you in terms of Grid and using it with different layouts like Flexbox as well. If you get concern over something or you find it hard let me know. Hope it will help you.

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

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