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

Testimonials Section

sttilstra•130
@sttilstra
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?

Actually getting the layout to be correct was challenging. I have not used grid before and it was a whole new thing.

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

Using grid in general. It took quite a few videos and assistant help to get things working. I have a better understanding of it, but still need to learn much more and be more comfortable with it.

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

Asking for help with the quotation mark image in the purple container. I could not get that looking right and excluded it on purpose. Any input on that would be appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•5,360
    @thisisharsh7
    Posted about 2 months ago

    Great job tackling CSS Grid for the first time and achieving a correct layout! Your layout looks clean.

    Suggestions:

    • Quotation Mark Image: To position the quotation mark in the .daniel testimonial, use a pseudo-element (::before) with background-image: url('./images/bg-pattern-quotation.svg'). Set position: absolute, top: 0, right: 10%, and adjust background-size and z-index to place it behind the text. Example: .daniel::before { content: ''; position: absolute; top: 0; right: 10%; ... }.
    • Grid Mastery: Simplify Grid layouts by using grid-template-areas for clearer structure. For .main_container, define named areas for each testimonial to make positioning intuitive.
    • Responsive Design: Enhance mobile responsiveness by adding intermediate breakpoints (e.g., 768px) to handle tablets. Use minmax() for flexible column widths.
    • Code Optimization: Group common styles (e.g., .testimonial padding, border-radius) to reduce repetition.

    Keep practicing Grid, and consider experimenting with Tailwind CSS for faster styling. Excellent work overall!

    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