Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 9 months ago

Responsive testimonials page using CSS grid

framer-motion, react, sass/scss, vite
Sarah•350
@Sarah-okolo
A solution to the Testimonials grid section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

The gridddd, really stressed me out. I didn't just want to make a static grid layout. I wanted something dynamic. Guess I shot myself in the leg with that one. Anyways, after much trial and error, I finally was finally able to get it right😊.

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

I would like feedback on the overall responsiveness of the site and on the accessibility as well. Thankss

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Michael•180
    @Networksentinel
    Posted 29 days ago

    Hi Sarah!

    I really liked your take on this challenge — the way the cards load when the page refreshes is cool!

    Also, I totally felt your pain when you wrote, “The gridddd, really stressed me out.” 😄 I could see it in your code, and honestly… same here! Grid layouts can be tricky, but you did a great job pushing through it.

    While going through your solution and checking out your code, I noticed a couple of small things — hope you don’t mind me sharing:

    1. Kira’s card not spanning as expected (600px–950px) At screen widths between 600px and 950px, the fifth card (Kira) isn’t spanning two columns — instead, it’s spanning two rows, probably because of this:

    @media (max-width: 950px) {
      .wrapper {
        grid-template-columns: repeat(2, minmax(250px, 1fr));
      }
      .card.style5 {
        grid-column: 1;
        grid-row: span 2;
      }
    }
    

    I think what you might’ve meant was:

    .card.style5 {
      grid-column: 1 / span 2;
      grid-row: span 4;
    }
    

    2. Layout gap between 950px–1250px In this range, there’s an empty space in the bottom-right corner of the grid. Not sure if that was intentional, but you could fill that space by either:

    • Spanning the 4th card (Patrick) across the 3rd column:
    .card.style4 {
      grid-column: span 3;
    }
    
    • Or making the 5th card (Kira) span three rows:
    .card.style5 {
      grid-row: 1 / span 3;
    }
    

    I know it’s been 8 months since you posted this solution, so maybe you’ve already spotted these things or would handle them differently now. Either way, I hope this feedback helps a bit!

    Also, if you do happen to see this, I’d love to hear how you’re doing now! How do you feel about this solution looking back? Would you change anything? I think it’d be super interesting to hear your perspective after some time has passed.

    Thanks again for sharing your work — and if you don’t get a chance to respond, no worries at all. Keep up the awesome work, and 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