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

Responsive testimonials grid using CSS Grid and Flexbox

Alice•170
@AliceeLe
A solution to the Testimonials grid section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm proud to use more responsive layout element like rem. Also, custom designs for each element is pretty laborious.

What challenges did you encounter, and how did you overcome them?

I was having trouble over having the grid keep its ration when adjusting the padding and margin. When I switched to rem instead of px, it works. I mostly google or search w3school for similar tutorials.

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

I'm still having trouble placing the quotation mark under the testimonial bolded text. I've tried using z-index and position:relative, but my code displays it as separate divs. Furthermore, I don't know how to make the pfp images more responsive when resizing. Would appreciate much help if anyone can help.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • N1Dovud•150
    @N1Dovud
    Posted about 1 year ago

    Hi! I personally handled the quotation mark by setting its position to absolute and specifying top and right properties. I also set its parent to relative so that its position is relative to its parent rather than the whole document. Apply z index of 1 to the svg and z index of 2 to the text that overlaps with the svg. I think there is much of a need for making pfp images responsive since they are almost always small and their size does not have to change really, but if you really wanted, you could give them a different width depending on the vw. I personally think the biggest problem you have is your paragraph contents whose font size depends on the vw. You probably wanted to make them responsive but as you go anywhere below 900 px, your text gets unimaginably small and thus illegible. In mobile screen, that's even worse. So, to fix it, just give a proper rem or font size in pixels. It will solve the problem. Good job, btw!

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