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

3 card layout , responsive with 1 line.

AaronKylePorche•65
@AaronKylePorche
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 really feel like I nailed this one! this is actually my second attempt because the first submit was a disaster. I didn't expect it, but the whole thing feels perfectly responsive with a display flex @media 800px and that's it. One thing that I could refactor for sure is to condense some classes. Also is there a different way to do the hover effect on the buttons? I had to hack the button padding to adjust for border height so it wouldn't break my card height...

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted almost 4 years ago

    Hey, great work on this one. Layout looks good in desktop, it is responsive and the mobile layout is good as well.

    Regarding your query:

    • Oh yes, a much simpler way. Instead of the padding and all of those. What you could just do is that. In the .btn selector, you should just add border: 2px solid transparent. This way the button already have the border. Then on the :hover state, you could just do:
    .btn:hover {
      border-color: apply the color needed
    }
    

    You only need that :>>

    Some suggestions as well would be:

    • On the main tag, the overflow: hidden; is not really being used, you could remove that.
    • On the body tag, to center the content, you should add min-height: 100vh on the body. Do not mistook this with height: 100vh okay, the latter is not advisable to use, use min-height: 100vh.
    • Avoid multiple h1 element on a webpage. Use only at least 1 h1. So change those car title into h2. Also just reminded, when using heading tags, do not skip a level. If you have h3 makes sure that h1, h2 are present.
    • Since you are changing h1 and h1 is needed in a webpage. On this one, the h1 would be a screen-reader only text. You could search for sr-only. That is just a css styling intended for screen reader. But if you are starting out, I wouldn't mind about it, but it is good that you are informed about it.
    • Those button should have been using a tags. Since the container itself is not really a form, button elements on this is not good.

    Aside from those, great work.

    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