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

Three Column Layout

Wesley Bobb•20
@WesleyBobb25
A solution to the 3-column preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


My main concern is I think the typography was a little bit off and do you think I needed to adjust the line height and/or the line spacing?

Also, I had to target the first and third column to apply the border radius as when I targeted the parent container (.cards) the border-radius property never seemed to work. Does anybody have an explanation they can help me out with?

Any other suggestions are more than welcome as I'm sure there are multiple errors here somewhere. :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kent O'Sullivan•1,870
    @12Kentos
    Posted about 3 years ago

    Hey @WesleyBobb25,

    Nice job on finishing this project! It looks great! :)

    As for your questions, yes I think the line height could be adjusted, but overall I think you did just fine on the challenge.

    Secondly, as for trying to put the border radius on the parent container, this will work just fine as long as you also set overflow: hidden;.

    The reason for this, is the border radius takes affect, but the child elements will overflow the container, as soon as you set the overflow to hidden, the corners that are overflowing the parent element will disappear and you will have rounded corners. :)

    lastly, I took a look at your code and I noticed you selected some elements directly like so.

    h2 { color: hsl(0, 0%, 95%); padding-left: 20%; text-transform: uppercase; font-family: 'Big Shoulders Display', cursive; font-size: 2rem; }

    I would highly suggest you avoid doing this, I understand this was a small project, so it doesn't really matter too much in this scenario, but if you get into the habit of selecting them directly like that, it Will cause you a lot of headaches in future projects where you have multiple h2 elements on the same page.

    Hope that helps!

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