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

Testimonials Layout using CSS Grid + Flex

Andi•140
@AStombaugh
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?

Despite a lot of struggling, I did finish the project and it looks...somewhat like the mockup. I am not well-versed with Grid yet and it shows. I think I made quite a few errors, but I stuck with it and finished and that's what I'm most proud of. While I did not have access to the tablet mockup, I did try to make sure the grid reduced appropriately regardless.

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

Working with the grid attributes to get the layout correct. This is the first time I've ever attempted this style of layout and it was very frustrating. I relied heavily on the browser inspector to give me a more visual idea of what was happening with my code as I was coding. The rulers and grid section numbering inside of Chrome's inspector was invaluable to this project, but also shows that I just don't have the experience with Grid yet to feel confident in doing it and doing it well.

What specific areas of your project would you like help with?
  1. What could be refactored in my CSS to make it simpler? I tried combining as much code as I could and ultimately found that I was overwriting myself as I was doing it which results in me splitting EVERYTHING into classes so I could better track where I was getting stuck. My primary cards have a total of three classes on just the top level card and that seems excessive.

  2. On desktop, what could I do to improve the handling of the grid layout? It feels very clunky to me. I'm not sure if that's just my lack of understanding the concepts of Grid or if I'm overthinking it. Realistically I would have liked this to reduce from desktop to mobile and back again with a little less reliance on media queries, but as I worked through this I genuinely could not figure out a way to make that possible. It feels like grid is intended to be very precise whereas flex allows you to utilize percentages and math to scale responsively.

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 Andi'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

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.