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

3-column preview card component

Alok Suman•2,360
@Alokray007
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 tried my best to get this design but I'm having issue while giving a height value to center card vertically. I used body { height: 200vh; } Please suggest what else could have been done to center card vertically and any other feedback on code will be much appreiated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Alper•1,090
    @adonmez04
    Posted almost 2 years ago

    Hi, @Alokray007. That's a good solution. Keep coding. Here are some quick tips.

    1 - Everything in your code looks normal. Maybe you can use this ruleset to center your content in the body instead of flex:

    display: grid;
    place-content: center;
    

    You can omit height: 100vh; or height: 200vh; because your content is high this default value (for mobile) and it makes some strange behavior.

    2 - You can add some margin values to your .cards class to make it easier to work with:

    .cards {
     margin: 88px auto;
    }
    

    3 - You can use this ruleset to set the button element to the default style:

    button {
        /* Button Style Reset */
        
        /* LAYOUT */
        /* Padding */
        padding: 0;
        /* TEXT */
        font: inherit;
        /* APPEARANCE */
        border: none;
        color: inherit;
        background-color: transparent;
        cursor: pointer;
    }
    

    However, you should add the type="button" attribute to your buttons in HTML to enable these styles, like this:

    <button type="button" class="your-class">Learn More</button>
    

    I hope these will help you. Keep coding and have a wonderful day.

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