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

3 Column Preview Card

Yuko-code•235
@Yuko-code
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 is my 2nd challenge. The first challenge took 3 days (!) but this time it took me less time, phew!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • tommynueve•25
    @tommynueve
    Posted about 4 years ago

    Hey, really good job overall! Some things that I noticed which require a bit of improvement:

    1. On desktop view, there is too much whitespace between the buttons and the end of the card, and maybe the margin between the button and the text could be slightly shorter. I noticed you used the card height fixed to 70vh, I will advise against setting card heights based on vh as it can make things stretch too much, you can just set them to a specific height and it will make your development resemble the design better.

    2. Buttons increase slightly on size when hover over them, and causes the button to appear as if it is moving down. That is because you are adding border on top of the actual height (In case you don't understand why, I recommend you check on the css box model). A little trick I learned over the years is to add the border to all buttons in their default state, and then on :hover you can just remove the background color (or set it to the same as the card), then they will all still have the same size. Bonus: adding cursor: pointer; to all buttons is normally a good idea.

    3. The contrast between font color and background color in the yellow card is too low, below accesibility guidelines, you need to darken it a bit. What I would do is to initially pick the same color as the card itself (at this point you won't be able to see the text as it will have the same color as the bg) and then with the color picker start moving it towards white, until you reach at least 4.5:1 contrast ratio. You will end up with a "yellowish-white". If you are just learning FE development, don't bother about everything accesibility related yet, but I do suggest paying attention to color contrast as it will grow on you to the point where you will spot it right away ;)

    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
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