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

Testimonials Grid Section (mobile first using grid and flex)

AKdeBerg•160
@AKdeBerg
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 have implemented the desktop version using Grid and the mobile version using FlexBox. Using two types of layout methods boosts my confidence.

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

In desktop version, an item wasn't stretching all the way through the whole cell. Later I found a property called align-items: stretch which solves the problem.

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

Box shadow is still challenging for me to apply. I can see the two white cards has some shadow, it's hard for me to apply. Anybody help me how to have that kind of shadow?

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Serhii Orlenko•415
    @grifano
    Posted 10 months ago

    Great job on structuring the testimonial section using the <article> tags—it really improves the semantic clarity! Just a couple of suggestions to make it even better:

    • Accessibility: Consider adding <header> tags for the card titles and using role="list" and role="listitem" for improved accessibility.
    • CSS Grid: Named grid areas could make your code more readable and maintainable, rather than relying solely on nth-child.
    • SEO & Performance: Implementing structured data for the testimonials could boost SEO, and using lazy loading for images might improve page speed.

    Overall, it’s looking solid! Just a few tweaks, and it’ll be even more robust. 😊

    Marked as helpful
  • Teodor Jenkler•4,040
    @TedJenkler
    Posted 10 months ago

    Hi @AKdeBerg,

    Nice project! I see you’ve put effort into accessibility, which is great. Here are a couple of tips for improvement:

    ARIA Labels: When using div elements instead of semantic HTML, consider adding descriptive class names to aria-label="". This will enhance accessibility and a quick fix—just copy the class name into the ARIA label.

    Font Weights: For an extra touch, you might experiment with font weights to get even closer to a pixel-perfect design. While not essential, it can help you achieve a near-perfect match with your screenshots.

    Hope these tips are helpful!

    Best, Teodor

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