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

HTML & CSS

buchi•60
@buchi-1996
A solution to the Social proof section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


please what's the best unit for font sizes (em or pixels)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • buchi•60
    @buchi-1996
    Posted over 4 years ago

    Thanks guys

  • David Payne•1,205
    @dpayne713
    Posted over 4 years ago

    Hey Buchi. I like to use REM as it references the root and scales for people who change their browser default font size.

    Check out this Link about it I found on the CSS tricks website

    https://snook.ca/archives/html_and_css/font-size-with-rem

  • Aleksandr Aksenov•750
    @axevldk
    Posted over 4 years ago

    Hi, @buchi ~ I have studied your work, and great work so far ~ Especially BEM naming is good. Here are some of my opinions.

    1. You can add min-height: 100vh; to body element, so that it can fit whole screen.

    2. In the top left text section paragraph is settled inside h1 tag. I am not sure why you did so, but this isn't good for HTML semantic rule.

    3. You used images tags for background but I think it would be better to use background-image css property or pseudo elements in such cases.

    4. You can set max-width: 1280px; margin: 0 auto; to your container element.

    Hope this will help you even a bit. Happy coding ~ ✨

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

Oops! 😬

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

Log in with GitHub