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

Testimonial section challenge, build with HTML,CSS,Sass

P
VirginiaPatrika•260
@VirginiaPat
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 liked the fact that I had to change the grid for different screen sizes. I also added another break point between tablet and desktop screen and adjusted the layout accordingly. Next time I will try to use sass. I am still learning but I think it will make things much easier and cleaner.

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

Trying to keep the dimensions analogy as shown in the figma file especially while changing the grid layout. Using grid-template-columns: auto; solved it.

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

Please any feedback will be much appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Kamran Kiani•2,780
    @kaamiik
    Posted 5 months ago

    Hi. Some notes for your code:

    • In each .testimonial, The person name can be a h2 tag as a heding.

    • Also you have two blockquote. So you can structure like this:
      <blockquote>
        <p>Bold text</p>
        <p>Regular text</p>
      </blockquote> 
      
      And for your css you can add this too:
      blockquote > p.regular::before {
        content: "" ";
      }
      blockquote > p.regular::after {
        content: " "";
      }
      
      This CSS does not allow the " select when you wanna select the text with your mouse.

    • Profile images do not need alt text. You can set it to alt="". Avoid using words like image, picture, or photo in alt descriptions.

    • For your CSS, There is lots of files and honestly It's really hard for me to find the problems. I think If you are using vanilla CSS It's better to wrap all of your code in one file or two file.

    • Generally from your preview I can say you only need a max-width on your section tag. You do not need min-width. And for your grid, You only need four columns and two rows and there is no need to define the rows height in your code. It's not true. Take this very simple and do not over complicate the code for your self.
    Marked as helpful
  • P
    Antônio Alves Cataldo•240
    @TonyzCataldo
    Posted 5 months ago

    Well, your design size is bigger than the request desktop design, outherwise your design is fine. keep coding.

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub