Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

Responsive 3 column preview card only CSS

sass/scss
Peally•200
@Peallyz
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


Nothing really hard (for me) except with the responsive where i have waste a lot of time. My render is not perfect under 1000 px.

I still enjoyed this challenge.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Travolgi 🍕•31,280
    @denielden
    Posted over 3 years ago

    Hey Peally, congratulations on completing the challenge! You did a great job 😉

    Let me give you some little tips for optimizing your code:

    • remove all margin from main tag
    • use flexbox to the body to center the card. Read here -> best flex guide
    • after, add min-height: 100vh to body because Flexbox aligns child items to the size of the parent container
    • use h2 for the titles of cards
    • use button for the learn more buttons and not a styled p
    • instead of using px use relative units of measurement like rem -> read here

    Hope this help! Happy coding 😁

    Marked as helpful
  • Vanza Setia•27,715
    @vanzasetia
    Posted over 3 years ago

    Hi, Peally! 👋

    Great work on this challenge! Your solution looks pretty good! 😀

    I recommend adding max-width to main element to prevent the cards from becoming too large on one column layout.

    Other recommendations from me.

    • For the "Learn More" buttons, I recommend using interactive elements such as link or button element. Remember, always use an interactive element if the element has interactivity.
    • In this case, all the car icons are decorative images so I recommend leaving the alt empty. This way, screen reader users won't have to listen to the unrelated or unnecessary content.

    That's it! I hope this information is useful! 😁

    Marked as helpful
  • Kamasah-Dickson•5,570
    @Kamasah-Dickson
    Posted over 3 years ago

    Your solution looks great bit on smaller devices you have to

    • reduce the margin left and right for your each container to have enough width, they look squashed together in small devices.

    • Remove any positioning property on the footer and just add text align center.

    Besides hope that was helpful. 👍 Good job, keep coding friend👍👍

    Marked as helpful
  • Peally•200
    @Peallyz
    Posted over 3 years ago

    Thanks you all for your tips I used most of all to correct my code.

    Have a nice day !

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