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

3-column preview card component

Ike•110
@ikeolu03
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


I had issue with making this responsive. There is a particular viewport that the middle column does not align with the other columns( to have an idea of what I am talking about you can check my screenshots folder).

Any suggestions on how to figure that out will be appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Carl•1,235
    @CarlHumm
    Posted about 2 years ago

    Here you go

    Basically you're setting align-items: center on your .container element which is aligning flex-children to the center based on their height. The height of the other two columns are greater because of the paragraph text, so SUV (With less height) is centered in the middle leaving a gap at the top and bottom.

    You can read more about it from the following:

    • MDN
    • CSSTricks

    You also set width to 800px (fixed) and max-width to 90%. This looks like a typo to me as it should be the other way around. You want the width to try and be 90% but no larger than 800px.

    If you want to align the buttons you can apply a margin-top: auto to space them apart from the top content, there are other ways to do this as-well.

    _nehal has already mentioned the issue with the border.

    Other than this, good job and good luck with making changes and your next project. :)

    Marked as helpful
  • _nehal💎•6,710
    @NehalSahu8055
    Posted about 2 years ago

    Hello Coder 👋.

    Congratulations on successfully completing the challenge! 🎉

    Few suggestions regarding design.

    • Use transparent border for no shifting of height on hovering buttons.
    .btn{   
    border: 2px solid transparent;
    }
    
    • Use background:transparent; on hovering don't use background-color specifically for each
    .btn:hover{   
    background:transparent;
    }
    
    • Use cursor:pointer for buttons for more user friendly.

    I hope you find this helpful.

    Happy coding😄

    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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub