Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

Testimonial section using CSS Grid

bem
R Hayes•240
@ryanthayes
A solution to the Testimonials grid section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I am not sure what is best practice for styling the individual testimonials sections. I chose to use "nth child" to select each and apply individual styles. Another approach could be individual utility classes for each. Which is the more standard approach?

It was my first time using grids for a design. Being able to span content across multiple cells (name?) and being able to rearrange the order of content visually will be very useful.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Riki Wendri•1,380
    @F4YY
    Posted over 2 years ago

    Hello there,

    Congratulations on successfully completing the challenge, you did great.

    I have a recommended approach that might interest you, using the Javascript arrays mapping for generating grid container style.

    Basically, arrays are a technique that can simplify the collection of data of similar type. in this challenge each testimonial data contains data with a similar pattern such as testimonial profile image, testimonial name, testimonial status (verified graduate), testimonial description and so on. What differs are the background color, the font colors, and a quote image in the first testimonial. You can add these to the data array. After the data is grouped into an array, then you can pass it as an object into a styled JavaScript mapping component inside each respective grid area.

    The code snippet could look like this:

                 return(
                     <Testimonialcard
                         key={testimonial.name}
                         $gridarea={testimonial. gridarea}
                         $namecolor={testimonial. namecolor}
                         $statuscolor={testimonial. statuscolor}
                         $maindescolor={testimonial.maindescolor}
                         $subdescolor={testimonial. subdescolor}
                         $bgcolor={testimonial. bgcolor}
                         $bgimage={testimonial. bgimage}
                     >
                             <Profilpicture src={require(`${testimonial.profpic}`)} alt={testimonial.profpic} 
                              />
                             <Quoteimage src={require(`${testimonial.bgimage}`)} alt= 
                             {testimonial.bgimage} />
                              <p>
                                     {testimonial. name}
                              </p>
                              <p>
                                     {testimonial. status}
                              </p>
                              <p>
                                     {testimonial. maindesc}
                         	  </p>
                         	  <p>
                                    {testimonial. subdesc}
                         	  </p>
                     </Testimonialcard>
    

    Hope that can be useful. Once again congrats and keep happy coding.

  • Lucky Avbunufe•190
    @Stanmancer
    Posted over 2 years ago

    Hello, R. HAYES,

    I believe using individual classes for each card/section is a better option in the long run.

    You might want to rearrange the cards later on or redesign a specific card, instead of going back to the html and editing the position of each card, you could just target the specific card that needs repositioning and do your magic.

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