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

Social proof using Flexbox

Joran Minjon•610
@DrKlonk
A solution to the Social proof section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I am mainly wondering if the way I did the background-images is the way to go.

I am trying to get better at naming classes, using the right HTML elements and accessibility, so it would be nice to get some pointers on that.

Any other comments are, of course, very welcome!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted over 4 years ago

    Hello, Joran Minjon! 👋

    Nice to see you complete another challenge! 😀 Well done on this one! 👍 Your solution looks good and responds well! 👏

    A minor suggestion I have is to add a max-width to the content of the page so that it doesn't become too stretched on extra-large screens. You might also want to add a max-width to the testimonial cards so that they aren't too wide when the layout first changes from desktop to tablet/mobile (that'll make the text inside those cards easier to read, too).

    Your placement of the background images seems good to me! 😀 I don't think you need have to include the "0"s in background-position: top 0 left 0, bottom 0 right 0 (you can simply have background-position: top left, bottom right) and I don't think you need to specify the sizes for the background images in this challenge (I think they are the correct size already and not defining their size in percentages will make them look more consistent across screen sizes—but they are background shapes that don't look bad even when skewed, so it might not matter too much). 😉

    Keep coding (and happy coding, too)! 😁

  • Grace•32,130
    @grace-snow
    Posted over 4 years ago

    Looks pretty good.

    Next time try mobile first instead and one definite change needed is swapping all alt="star" for alt="".

    I don't think it's valid to have header elements inside list items. I would use divs instead, as extra banner roles (headers) can actually cause problems for assistive tech navigating the conteng, not help those users. Not a massive issue but something to be aware of.

    Good job

  • Joran Minjon•610
    @DrKlonk
    Posted over 4 years ago

    Thanks both! I made the updates and changes. Ready for shipping now ;)

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

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

Log in with GitHub

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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