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

Responsive Testimonials section using CSS Grid

P
Kyle Mulqueen•400
@kmulqueen
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? What I'm most proud of, and what I'd do differently

I'm most proud of creating a visually accurate implementation that maintains proper spacing and proportions across different viewport sizes. The quote SVG positioning worked particularly well as a decorative element that enhances the design without interfering with content readability after applying proper z-indexing.

For future projects, I would approach the testimonial grid items differently by using more semantic class names instead of relying on nth-child selectors. This would improve maintainability and make the code more adaptable to content changes. I would also establish a more structured CSS architecture from the beginning to reduce redundant code.

What challenges did you encounter, and how did you overcome them? Challenges encountered and solutions

The main challenge was positioning the decorative quote SVG in a way that wouldn't interfere with the text content. Initially, the SVG was appearing on top of the text, making it unreadable where they intersected. I solved this by:

  1. Setting the position of the testimonial to relative
  2. Using proper z-indexing to ensure the SVG stayed behind the text

Another challenge was creating the responsive grid layout that would accommodate varying content lengths. I overcame this by implementing a flexible grid system with specifically defined grid areas rather than relying solely on auto-placement.

What specific areas of your project would you like help with? Specific areas where I'd like help

I would appreciate guidance on:

  1. Best practices for organizing grid items without heavy reliance on nth-child selectors
  2. Techniques for creating more accessible decorative elements that enhance design without impacting usability
  3. Approaches to streamline responsive layouts with fewer media queries
  4. Strategies for making the layout more resilient to content changes and additions
Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Kyle Mulqueen's solution.

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.