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

3 Column Preview Card Component

Jonathan•105
@JonMStevens
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 did this challenge to try and get more comfortable with CSS grid. Any feedback is appreciated, and feedback about grid is particularly welcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Brooke Wargnier•155
    @brookewargnier
    Posted almost 4 years ago

    Hey JonMStevens!

    Really great job using grids on this project. I love that everything smoothly transitions in sizing. I have two quick suggestions to help improve!

    1.) I'd look into keeping the height proportional and also shrinking as the display shrinks. You could set up a few different break points to help with the transition between desktop, tablet, and mobile.

    2.) This ties into the first tip! There are really great theories on balancing how many characters you keep per line and I think these get a little squished in that middle ground (tablet world). This link does a really great job at explaining the optimal characters per line of text so everything still reads nicely:

    https://www.smashingmagazine.com/2014/09/balancing-line-length-font-size-responsive-web-design/

    If you set up the different break points, you can also transition your text to get smaller gradually in order to avoid lines with only 13 characters when the optimal is 45-75.

    Otherwise I think you have a really great little project here and I look forward to seeing what you do next!

    Marked as helpful
  • Ramiro Solano•35
    @ramirisho
    Posted almost 4 years ago

    The background color of the buttons must be the same white as the title.

    Marked as helpful
  • Erick F. Felix•265
    @efs0-cod3
    Posted almost 4 years ago

    Your code looks great you should check some things like border radius and their position and the position of the attribution Instead of div I would change it to footer. Otherwise is looking good minor things. Hope it helps.

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

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