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

Mobile & Desktop 3 Column Preview using HTML & CSS

Aimee Ortiz•110
@BeetleJeuse
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 had a lot of trouble going from mobile to desktop with this project. I still notice a discrepancy with my grid items when I slowly expand my screen. The items are different sizes before expanding to their max-width. Is there a way to fix this ? I used display: grid for desktop because when I was using flexbox, only the Sedan section was larger than the others and I couldn't figure out why. If anyone could take a look at my code and offer suggestions, I would really appreciate it. This was a hard project for me. Thank you!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kent O'Sullivan•1,870
    @12Kentos
    Posted about 3 years ago

    Hey @BeetleJeuse,

    Nice job on completing the challenge, it looks good! So I figured out what is causing the issue. If you inspect your page, on the main container you have the following property. align-items: center; as you shrink the page down if you notice the <p> elements in the SUVS and the Luxury sections grow to have a fourth line before the Sedan section does. Because of this, their container box is slightly larger than the Sedan one. Since the main-container is aligning them to the center, and the Sedan section is now slightly smaller than the other two cards it gets aligned to the center. I hope that made sense? Haha if not let me know, and I'll see if there is another way I can explain it.

    Keep up the good 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

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