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

3-column preview card component using HTML & CSS Flexbox

Moises•60
@devmoises
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


This challenge is very interesting, it has its details to consider, I really liked it. I await your advice and recommendations. Thanks.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grzegorz Sterczewski•680
    @gsterczewski
    Posted about 4 years ago

    Hello Moises 👋, my name is Grzegorz.

    You did really good job, and implemented the design almost perfectly.

    One minor thing to improve is to add focus state to the anchors, so user can navigate it with keyboard.

    Of course those links are dead, but I think it is a good practice to remember about a11y (I'm working on it myself).

    Overall, excellent work, I'm hoping to see more of your work here.

    Keep up the good work! 💪

    See you on the coding trail 😉

    Cheers!

    Marked as helpful
  • ToNisamBioJa•330
    @ToNisamBioJa
    Posted about 4 years ago

    Hello!

    Really good job on this one. You got it really close to the original design and added a nice hover animation.

    The only thing you could change is the border radius but thats about it.

    Keep it up! Happy codding!

    Marked as helpful
  • David•175
    @Dups11
    Posted about 4 years ago

    Hi, just a little improvement :

    For better results with border radius you should :

    1. Border-radius: 10px on section "cards" not on the "card_items"

    2. overflow-hidden on section "cards"

    Apply this rules after remove all other border-radius.

    Marked as helpful
  • P
    Patrick•14,265
    @palgramming
    Posted about 4 years ago

    Really slick hover animation. Great Job 🌟🌟🌟🌟🌟

    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

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