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

Four Card Feature Section

Vinit Gupta•20
@thevinitgupta
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I faced a problem that I was not able to fix. The two cards on the side were not placed as mentioned in the problem. Can you help me find the problem?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Leshy•580
    @LeshyNL
    Posted about 5 years ago

    Hi Vinit Gupta,

    The issue is that your card section is 100% of the width of the screen and each column is 33% of the width of that. With the cards being centered in each column, that means that they will move far apart as the columns get wider.

    You can fix your approach of using three columns set to display: inline-block by removing the width declarations on the columns, and setting text-align: center on the card section div. You will then need to add some margins to your cards to ensure that there is some space between them.

    However, you will notice that the layout breaks as you go to smaller layouts, and have to do more work to fix it for those. What you will want to do for this challenge, is look into CSS layout techniques, such as Flexbox.

    It will take a bit of learning and practicing to become really good with it, but it will make this challenge quite easy. See for more information https://css-tricks.com/snippets/css/a-guide-to-flexbox/. Once you have a bit of an idea how it works, https://flexboxfroggy.com is a fun way of practicing with it.

    It's a very good first attempt though, so keep going! :)

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