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

Testimonials Grid Section Using Pure CSS

Nathasha•150
@NathashaR1997
A solution to the Testimonials grid section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey Everyone, I have completed the Testimonials Grid Section challenge.

Check out my following article, where I have briefly explained the steps I have followed to complete this challenge.

https://medium.com/ux-planet/challenge-010-testimonials-grid-section-9067105b9ff

Thank you for checking this out, and feel free to leave your feedback and thoughts!! Any feedback and tips are welcome.

Many Thanks! Nathasha 😊

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Shalom2935•420
    @Shalom2935
    Posted about 2 years ago

    Hey @Nathasha, I really like the way you explain every step of your code. Some ideas to improve your code:

    • Wrap the code inside the body in a main element instead of a div; that will make your code more semantic therefore fix the accessibility issue.
    • The .parent-wrapper element is too wide, give it a width of 80% instead of max-width:1440px.
    • I think doing it with flexbox is too much work, learn the css grid and you will see how simple it could have been.
    • There is quote in the background of .daniell-tetional-wrapper that you missed. Two ideas to help you choose what suit you the most. 1- give the .daniell-tetional-wrapper a relative position, give the quote you want in the background an absolute position; use top and right properties to adjust his position, then use the z-index so that the quote will be beneath the text. 2- place the quote as the background-image of .daniell-tetional-wrapper, then adjust his position with background-position: top; and background-position-x: "value_that_will_work".
    • Your responsive is designed only for large and small screen's size, it would be very nice if you added a medium size screen.

    I hope my comments will help you somehow, happy coding journey.

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