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

testimonial grid section with tailwind, grid and flex-box

tailwind-css
P
Smaylen5•600
@Smailen5
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 that I aligned the cards correctly using grid. Next time, I'd like to change the default font size to be more similar to the layout.

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

The biggest challenge was creating a layout that didn't break on tablets. Unfortunately, I couldn't solve the issue; I think I need to set minimum sizes, but the text was overflowing from the cards.

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

How to create the layout for tablets so that it doesn't break on desktop.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • James Brown•260
    @jamesbrown173
    Posted about 1 year ago

    **Design: Good! Clean easy to follow. Maybe consider using a lighter font in the lower paragraphs.

    **Code: Well commented, easy to follow.

    You mentioned the text overflowing, if you remove the lg:h-full class in this div it should stop the text from overflowing. I think when you're using lg:h-full it expands the div to the full amount of the parent, in this case the parent is restricted in size by it's padding, I think, therefore the text overflows.

    <!-- Contenitore generale per grid --> <div class="lg:w-10/12 lg:h-full grid lg:grid-cols-4 lg:grid-rows-2 lg:gap-8 gap-6">
    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

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