Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 23 days ago

Testimonials grid section main using CSS Grid

Leyanis Díaz•220
@LeyaDiaz
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 am most proud of successfully implementing CSS Grid in a real-world project. It was my first time applying Grid to create a complex and responsive layout, and seeing the design come to life exactly as intended was very rewarding. The challenge helped me deepen my understanding of grid areas, row and column spans, and responsive adjustments.

Next time, I would spend more time planning the grid structure before coding to avoid some trial-and-error. Also, I would integrate more fluid units like minmax() and auto-fit earlier to make the layout even more flexible across different screen sizes

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

The biggest challenge was mastering CSS Grid’s syntax and behavior, especially when positioning elements that span multiple rows and columns. Initially, some cards didn’t align properly or had inconsistent heights.

I overcame this by studying documentation, experimenting with different grid properties, and using browser developer tools to inspect the grid layout visually. I also sought examples and tutorials to understand best practices for responsive grid design

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

How to make the grid adapt smoothly between breakpoints without abrupt layout shifts.

Best practices for equalizing card heights dynamically without fixed heights.

Suggestions for combining CSS Grid and Flexbox efficiently inside cards for content alignment.

Any tips or code examples to improve these areas would be very helpful!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Asya0601•280
    @Asya0601
    Posted 23 days ago

    The work is almost identical to the layout, great job! I would only change the background color to Gray 100. As for smoothness, you can set the width of the container relative to the screen, so that when the screen resolution decreases, the container follows it in percentage terms. The width can be set differently at different intervals between breakpoints. Code example(mobile-first):

    .main_container{ width:90%; }

    @media(min-width:768px){ .main_container{ width:80%; } }

    @media(min-width:992px){ .main_container{ width:70%; } }

    @media(min-width:1200px){ .main_container{ width:60%; } }

    In this case, you also need to adjust the height, for example, through the margin-block of the container.

    Happy creating!😀👍

    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