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

3 Column Preview Card Component using FlexBox

spyder•315
@ratan17
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


Please take some time to review my work. I would like to hear from you guys 🙏

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • darryncodes•6,350
    @darryncodes
    Posted almost 4 years ago

    Hi Spyder,

    Good work on your solution.

    A couple of observations at a glance from me:

    • you could add a hover affect on <button> to match the design. Set a transition property so when the user hovers over the button the hover affect is smoother for example: transition: .3s; or transition: ease-in .3s;
    • don't forget to add background: transparent; and the relevant font color: color: hsl(0, 0%, 95%); to the hover state
    • as you're using flexbox you could use align-self: start; on the button so on mobile it doesn't span all the way across the card like on the design. you'll need to play around with the padding left & right to get the right button size though

    Happy coding!

    Marked as helpful
  • Yashasvi Singh•890
    @aUnicornDev
    Posted almost 4 years ago

    You have used position: absolute; on the Learn More button with a bottom:5%.

    This takes the button out of the normal flow of the card and fixes the button on the card. Changing the height of the button will not affect the height of the .items

    So, the content that remains in the card is just the SVG, the heading and the paragraph and the button is placed in the 5% padding given to .items

    When on smaller viewport, the value of 5% decreases, whereas the the dimensions of the button remain the same.

    Head over to my solution if you like, I've used flex in the card itself.

    Marked as helpful
  • Yashasvi Singh•890
    @aUnicornDev
    Posted almost 4 years ago

    On smaller screens, the buttons are overlapping the content of the card because of the absolute positioning given to them.

    Instead, use flex on the .items class so that you can position them in accordingly.

    Set a max-width to the cards as they keep on stretching on bigger screens.

    Marked as helpful
  • spyder•315
    @ratan17
    Posted almost 4 years ago

    I have UPDATED MY SOLUTION GUYS !! PLEASE HAVE A LOOK

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

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

Oops! 😬

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

Log in with GitHub