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

testimonials-grid-section

EmicJoykiller•270
@EmicJoykiller
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’m most proud of the responsiveness and visual coherence of the "Testimonials Grid Section." The layout adapts seamlessly across various screen sizes, providing an optimized user experience regardless of the device. I’m also proud of how clean and modular the CSS is, which will make future updates or scaling easier.

If I were to do something differently next time, I would consider implementing a JavaScript-based feature to add interactivity, such as animating the testimonials as they enter the viewport or integrating a carousel effect. This would enhance the overall user engagement and make the section more dynamic.

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

One of the key challenges was ensuring the grid layout maintained its structure across different devices while keeping the design visually appealing. Some testimonials needed to span multiple columns, which required careful manipulation of the grid areas.

I overcame this by using media queries combined with CSS Grid properties like grid-template-areas. By breaking down the grid into manageable sections, I could easily adapt the layout for different breakpoints. Testing on various devices also helped to fine-tune the design.

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

I would appreciate feedback on improving accessibility in this project. While I’ve ensured the layout is responsive, I want to further optimize it for screen readers and keyboard navigation. Additionally, I’d like help integrating interactive elements, such as animations or user-triggered events, to make the user experience more dynamic and engaging.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mudasir Nadeem•430
    @mudasirNadeem
    Posted 8 months ago

    Your semantic HTML is well-structured, but adding alt text for images and improving keyboard focus states would enhance accessibility. The layout is responsive, though testing on larger screens could help optimize design flow.

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub