Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 3 years ago

Testimonials grid section using CSS Grid

Aram•280
@OhSorrow
A solution to the Testimonials grid section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Please take a look at my HTML code and suggest any improvements. I appreciate it!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Lucas 👾•104,160
    @correlucas
    Posted almost 3 years ago

    👾Hello Aram, congratulations for your new solution!

    You've a great solution here and I can see you paid a lots of attention for everything. The grid layout is fully responsive and the media query is working fine! The only thing to improve is the amount of div you've used here, note that many of these card elements can stand alone without a div to wrap it, the only block that really need a div is the block with the profile photo + job title, if you delete these unnecessary divs you'll reduce a big chunk of code since this divs will repeat around all the cards.

    ✌️ I hope this helps you and happy coding!

    Marked as helpful
  • romila•3,550
    @romila2003
    Posted almost 3 years ago

    Hi Aram,

    Congratulations 🎉 for completing this challenge, the Testimonials looks great and is responsive. There are some issues regarding your HTML, and CSS I want to address:

    1. Since you are using the article tag, you need to include the heading tag which can vary from h2 to h6
    2. In desktop, I would strongly suggest you remove the padding property from the main tag since it is creating an overflow, where users would have to scroll down the page to see the bottom of the cards.
    3. To prevent the cards from being too wide, you can give the main tag a max-width of 1440px.

    Overall, great attempt and wish you the best for your future projects so keep coding 👍.

    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

Oops! 😬

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

Log in with GitHub