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

SOCIAL PROOF SECTION using Flexbox

Ken•935
@kenreibman
A solution to the Social proof section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Did this with Flexbox because I am still not comfortable with Grid. This definitely felt like a project that would have been easier using CSS Grid. A lot of videos/resources on learning grid are a little confusing - If anybody has any good resources that helped them, that would be great. I know grid is very powerful when used correctly.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Orlando Guevara•220
    @coding-tomato
    Posted over 3 years ago

    To your question, have you ever tried Grid Garden? Kickstarted me into realizing how good Grid is for like... A lot of things!

    Marked as helpful
  • P
    Ken•4,915
    @kens-visuals
    Posted over 3 years ago

    Hey @lmaoken 👋🏻

    I have some suggestion to help you fix the accessibility issues and some other things.

    • In your markup, <div class="container">...</div> should be <main class="container">...</main>. This will fix the accessibility issues. Just, don't forget to generate a new repot once you fix the issues.

    I hope this was helpful 👨🏻‍💻 I don't have any special grid video suggestions, however I know whom you should follow for that type of content. And that creator is Kevin Powell, he's the one who talks about them a lot. I agree grid is more complex and harder to grasp than flexbox, but it just takes some time, once you grasp the core concept you'll see how easy it is. Also check out Frontend Mentor's resources page, there are some cool things about grid and to practice grid. One last suggestion would be to make the animation a little bit faster, also nice touch on that one. Other than that, you did a great job, even with flex box, keep it up. Cheers 👾

    Marked as helpful
  • Ken•935
    @kenreibman
    Posted over 3 years ago

    Also someone please help me with the 6 Accessibility Issues!!

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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