Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Made with css grid (and added a small animation for the first time!)

JanAbe•230
@JanAbe
A solution to the 3-column preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • solvman•1,650
    @solvman
    Posted over 1 year ago

    Hi @JanAbe 👋

    Very well done! 👍 Congratulations! 🎉

    I have a few minor suggestions that might help you to improve your project:

    • ⭐️ Consider swapping background color with text/button color. The background color should be lighter than the text/button color.
    • ⭐️ There is a minor clipping issue when the width is 670px to 600px. That is caused by the fact that there is no space left to shrink the width anymore due to the fixed button size and padding/margin around it. There are a couple of ways you can address it. One way is to add min-width (it will add an annoying scroll bar at the bottom). Or you could make your whole layout jump to mobile at 670px vs 600px.
    • ⭐️ There is a button shifting issue on the widths of 702px-713px, 818px-794px, and 990px-950px. That is caused by the hard-set margin-top on your button element. Perpahs, consider making each card a flex/grid container and adding align-self: flex-end to the button class to make buttons "stick" to the bottom of the container.

    Otherwise, great job! 🎊 I hope you find my comments useful 🫶

    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