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

3 Column Preview Card Component using Flexbox

Ken•935
@kenreibman
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 feel myself getting better at this and hoping that I reached the desired result on my first attempt.

If anybody has any criticism, advice, or feedback. It is so greatly appreciated if you could take some time out of your day to leave a comment. I am doing my absolute best to improve everyday.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • CyrusKabir•1,885
    @CyrusKabir
    Posted almost 4 years ago

    hello my dear friend ♥ your cards at all are good and clean but here some tips :

    • we can't see any hover state in your code
    • and it's better to keep cards in this design in row when viewport it's more than 1000px or something like that you know what i mean but at all it's good but try to improve it for sharping your skills ♥♥♥
    Marked as helpful
  • Ken•935
    @kenreibman
    Posted almost 4 years ago

    Does anybody have advice on how to have the content align with the original design properly?

    I made sure to have a container surrounding the main card component. I set the container height to a 100vh and justified its content center to center the main card in the middle of the page(justify-content: center;) -- yet my result seems to be a few pixels above the original design.

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