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

Responsive page using media Query

accessibility
Amobi Jonathan Chukwudi•350
@Jonathanthedeveloper
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


Pls Guys this streesed me a lot Review my code and let me knowthe best way i should have done it

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • foxynoxy•470
    @purplehippo911
    Posted about 3 years ago

    Hi @Errorman2003. Congratulations on finishing with this challenge.🎈🎆🎇

    As for the problems in this solution, you can start by removing the margin-top:50% from the first section. I know your trying to center it but I can help you with that. So instead you can write in margin:5rem auto;. This will put a margin of 5rem at the top and the bottom and a margin of auto on the left and the right.

    And you should also remove the height:max-content;, because it doesn't do anything for your section, and because adding heights make your webpage unresponsive, and then you will have to rewrite it in the media queries. So you should not use height where its not needed and you can also use padding instead. So your section should look like this.

    section {
      color: hsl(0, 0%, 95%);
      width: 80%;
      margin: 6rem auto;
      font-family: "Lexend Deca", sans-serif;
      font-size: 15px;
      max-width: 1000px;
      display: flex;
      justify-content: center;
    }
    
    

    And of using position relative, for aligning the buttons, you can use flexbox, and add display:flex; in your cards. For example:

    .sedan {
      width: 230px;
      background-color: hsl(31, 77%, 52%);
      padding: 3rem; 
      border-radius: 8px 0 0 8px;
    }
    

    And remember to do the same with .luxury and .suv.

    .learn {
      padding: 0.5rem 3rem;
      background-color: hsl(0, 0%, 95%);
      border-radius: 20px;
    

    And instead of using section for the footer, you can use the footer-element, because this way just feels more right.

    <footer class="footer"> 
    
    </footer>
    

    If you misunderstood anything I said then you can just write to me here. And I would recommend you to check out Kevin Powell's free course on responsiveness here:

    Responsive course

    Well done, with this challenge.

    Cheers.

    Marked as helpful
  • foxynoxy•470
    @purplehippo911
    Posted about 3 years ago

    Hi @Errorman2003. I saw that you made some changes and I can already see some good improvements. Good job, and thank you for marking my comment as helpful. I´m happy that I was able to help.

    But there´s a last step you forgot to do, because here at frontend mentor your solution still looks the same because you haven´t updated the screenshot at the desing comparison-section at the top of this page. Under the desing comparison-section, there´s a button which says update screenshots. Push that button and the screnshots at the desing comparison- should update.

    Happy coding.

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