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

Four card feature solution (float layout)

Habeebullahi Olalekan Lawal•70
@Habeebullahi01
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


It took me some time to find a way to vertically align the cards. And I also struggled with using media queries, (1440px didn't seem to do it). It worked fine locally but it didn't when I put it on github and vercel. Please help me anyhow you can.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Martin•1,150
    @ringm
    Posted about 5 years ago

    Hey Habeebullahi, great work! I think the overall layout of the site looks good. And it's also responsive, congratulations.

    I checked your code and I think you could achieve a better result using flexbox instead of floats. You could try something like this:

    .cards {
      display: flex;
      flex-direction: column;
      align-items: center;
    }
    
     @media (min-width: 600px) {
      .cards {
        flex-direction: row;
      }
     }
    

    That should do the trick! In small devices your cards will display one below de other, and when the screen hits 600px size (you can change that if you like) they will display like the big screen layout.

    Also, I leave you here a short article that explains all the different ways you can vertically center an element.

    I hope it helps! Good luck and happy coding :)

  • Israel B Lewis•10
    @blewis-1
    Posted about 5 years ago

    I used the transform:translateY and translated(moved) it by 50% upwards. I added a class on both containers that needed to be vertically aligned. Note: I used flex-box.

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