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

Social proof section using Grid and Flexbox

Maria Urdapilleta•55
@mariaUrda
A solution to the Social proof section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Feedback will be appreciated :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Renszo Camacho•1,615
    @RenszCamacho
    Posted over 4 years ago

    Hiya 👋🏻 mariaUrda. Well done my friend 👏👏👏. You have done a fantastic job on this challenge 👌, and it’s responsive 💯.

    Just I few suggestions in my humble newbie opinion. 😊

    The backgrounds-images are not in place, at least not on my screen, so it looks good on all screens. I would give the body a min-height: 100vh

    Your user testimonial images are slightly big, I would do something like this:

    .card-bottom-picture { border-radius: 50%; width: 3rem; height: 3rem;

    Hopefully, it helps.

    Happy coding🧑‍💻

  • Szymon Rojek•4,540
    @SzymonRojek
    Posted over 4 years ago

    Hi Maria,

    Well done :D, good job!

    I have checked your HTML and have a few tips for you if you don't mind:

    • you have used so many divs but we have also semantic tags. Divs are semantically inert elements — elements that don’t really do or say anything, of course, they are important too. You can change a bit the HTML structure by using semantic tags;
    • don't need to use words like picture or image, photo, icons in the alt text as it's already announced as being an image => we can easily type the name like alt="Jonathan" etc; Also, it is good to ask what kind of role img does have, for example: if we have decorative img - in these cases, a null (empty) alt text should be provided (alt="") so that they can be ignored by assistive technologies, such as screen readers;
    • you didn't use the main h1: just to let you know, you should only use one h1 per page. Using more than one will not result in an error, but using only one is seen as a best practice. It makes logical sense => h1 is the most important heading, and tells you what the purpose of the overall page is (generally please read about headings h1-h6);
    • you have got HTML issues report above (please fix the code as recommended);
    • I suggest that you can familiarize yourself with BEM naming convention (after using it you will see many profits);
    • design: from mobile size till 1000px is a huge gap so you can work still on RWD for tablets (check it out by the inspector);

    Finally, congrats! Please, don't forget to upvote any comments on here that you find helpful. That's it from me. Hopefully, it will help you.

    Greetings :D

  • Teddy K•30
    @dev-ted
    Posted over 4 years ago

    Hi Maria, this is really good You write clean and readable CSS Keep it 🔥🔥🚀🚀🚀

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

Oops! 😬

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

Log in with GitHub