Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

Testimonials grid section

Julian Balaguera•160
@julianchoripan
A solution to the Testimonials grid section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What specific areas of your project would you like help with?

it seems that I'm unable to understand what rem and em are and when to use them :sob:

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•3,850
    @thisisharsh7
    Posted about 1 month ago

    Great work on your project! The CSS and HTML are well-structured, and regarding your question on rem and em:

    • rem (root em): Use rem for things like spaces or font sizes when you want them to stay the same everywhere. This is like a ruler that measures everything based on one big size—the size set at the very top of your webpage (the <html> tag). Usually, this is 16 pixels (px). So, if you say 1rem, it’s 16px, no matter where you are on the page.

      Example: If you set font-size: 1rem on a title, it’s always 16px (if the root is 16px).

    • em: This is like a ruler that changes based on the parent (the box your text lives in). If the parent’s font-size is 20px, then 1em equals 20px. Use em when you want sizes to depend on the parent’s size, like making text or spacing grow or shrink with it.

      Example: If a parent has font-size: 20px, then padding: 1em means 20px of space.

    • How they help in responsive design:

      • rem: Makes your site look great on all devices because you can change the root font size (in <html>) for smaller screens. For example, set html { font-size: 14px } for phones, and all rem sizes shrink automatically, keeping everything proportional.
      • em: Helps parts of your design (like buttons or text inside a box) scale with their parent’s size. If you make the parent’s font smaller on a phone, em sizes adjust too, making things fit perfectly.

    Try this:

    html { font-size: 16px; } /* Default for desktops */
    .parent { font-size: 20px; }
    .title { font-size: 1rem; } /* 16px on desktop */
    .text { font-size: 1em; } /* 20px, follows parent */
    @media (max-width: 600px) {
      html { font-size: 14px; } /* rem shrinks to 14px on phones */
      .parent { font-size: 18px; } /* em adjusts to 18px */
    }
    

    Hope this helps-Keep up the great work!

    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