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

Testimonials grid section - Responsive

Donovan Romero•100
@nsvonod12
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?

The use of grid

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

No problems

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

None by the moment

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sardor Akmalovich•190
    @akmalov11c
    Posted about 1 year ago

    Hi there! You've put together a visually striking layout with engaging content. Here's some feedback to help refine your project:

    HTML:

    1. Your HTML structure is well-organized and uses appropriate tags. However, you could enhance accessibility by including alternative text for your images using descriptive alt attributes.
    2. Consider utilizing semantic HTML elements such as <article> and <figure> to provide more meaning to your content, especially for screen readers and search engine optimization.

    CSS:

    1. Your use of CSS variables is excellent for maintaining consistency and making updates easier. Consider giving your variables more meaningful names to improve readability and maintenance.
    2. You're effectively applying responsive design techniques with media queries. However, ensure that your media query syntax is correct (e.g., @media (min-width: 1200px)) to properly target larger screens.

    Overall, you're off to a great start! Keep experimenting with design and layout to enhance user experience, and continue honing your skills. Happy 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