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

Social proof section HTML & CSS FlexBox Solution

Antonio Scardovi•40
@antonioscardovi
A solution to the Social proof section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I had trouble with background images, what's a better solution for them? I also noticed the testimonial cards are not responsive in production, I couldn't get them to automatically center with flexbox, any suggestions here?

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Anna Leigh•5,135
    @brasspetals
    Posted over 4 years ago

    Hi, Antonio! Hopefully I can help with some of your questions. 😃

    If you remove height: 100vh from the body, your background images will display correctly.

    While this won’t fix everything, I worked with your code a bit and found some things that will help with general alignment:

    • Adding a padding to your section element. This will help the top and bottom sections line up better.
    • Removing height: 50vh from top and bottom divs will also help with responsiveness.
    • Removing all the margins from top-left, title, and description

    The testimonials are not responsive because you have given them a specific height and width. Using max-height or max-width would probably be better, but you may have to play around with the values. I also suggest changing the bottom to just the following:

    .bottom {
        display: flex;
        justify-content: space-between;
        align-items: center;
    }
    

    To get the first testimonial to line up with the top, you will have to remove its margin-left.

  • Dawid•440
    @dwddgsz
    Posted over 4 years ago

    Hello

    At this (max-width:768px) you can try add margin:0 auto to .bottom .test. It should do the job. Keep up good work

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub