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

Testimonial Grid Section Responsive Layout using Grid and Media Query

P
Ethan John Paguntalan•260
@dev-ethanjohn
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?

Getting more comftable with CSS grid and media query. I would explore in the future using Javascript to dynamically adjust sizing and location of components.

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

I got into an issue where my CSS for the part of individual styling of cards is becoming more lengthy. Luckily I was able solve it by building a more robust selector by just utilizing locally declared custom properties. By creating a locally scoped variables, I was able to modularize individual cards.

.testimonial-card:nth-of-type(1) {
  --testimonial-bg: hsl(var(--clr-purple-500));
  --testimonial-highlight-clr: hsl(var(--clr-white));
  --testimonial-detail-clr: hsl(var(--clr-purple-50));

  --author-name-clr: hsl(var(--clr-white));
  --author-status-clr: hsl(var(--clr-purple-50));
  --img-border-clr: hsl(264, 82%, 70%);
}

taking advantage of shared styles such as the ff:

/*shared styles for author info texts*/
.author-name {
  color: var(--author-name-clr);
}
.author-status {
  color: var(--author-status-clr);
}

There are many more robust solution and even more outside of plain CSS, but this gets the job done for now.

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

I would love see any feedback on responsiveness and maybe further recommendations that I may check out for.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mathieu-310•180
    @Mathieu-310
    Posted 5 months ago

    Hello!

    You did it :) great job!!

    ✔ You forgot to add the title of the page

    ✔ You used h1, h2 and then hide them in css, I guess you're worried about accessibility, but I think here it's just a block and in it there are divisions just to be able to style them and so there's not really a need to use semantic tags. Indeed semantic tags are parts of a website in their own right but here it's just a single block so you can give it a semantic tag and the rest used generic tags for style reasons. So you shouldn't use semantic tags anywhere, you should rather understand the major sections of the website and use them if necessary.

    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