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

Social proof page with Grid and Flexbox

bem
Jason Greenwald•200
@jaycgreenwald
A solution to the Social proof section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


  1. Would it be better if I had used a header tag for the title section?
  2. I converted almost all my px values to rem. Overkill or good job?
  3. When I change screen width, the background "moves" relative to the page content. Is this okay? Or should they stay in the same place relative to the content?
  4. To test my changes, I take screenshots of the page then reduce the opacity and lay them over top the design images to evaluate how they match up. (I do this in Illustrator.) Is there a better way to test changes?
  5. Anything else you can share with me. Thanks!
Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Karol Binkowski•1,620
    @GrzywN
    Posted about 3 years ago

    Great job!

    1. You can use header tag, it's more about how you see your site than something being correct or not correct. If you see your project being section for some other page you can wrap everything into main tag as you did. If you see your project as a whole website, you can use header instead.
    2. Great job, as you did, you should use rem units all the time. Sometimes pixels are converted to rem with precision loss, so be careful. You can use VS Code extension to alternate between px and rems with one keyboard shortcut.
    3. I think it looks great, you can take a look at other solutions to see how others handled this thing.
    4. To match the design with your project:
    • you can set your background to design image
    • you can use DiffChecker website
    • you can use PerfectPixel extension for Google Chrome

    Hope this helps! Keep coding and have a nice day!

    Marked as helpful

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