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

Testimonials Grid Using CSS Grid

Abdulwahab Sani•125
@aabsani
A solution to the Testimonials grid section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


The background quote marks for the top left div simply wont show. I have double checked the url to make sure the path name is correct but still isnt visible. The image doesnt apppear anywhere on the page. Help please?

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdulwahab Sani•125
    @aabsani
    Posted about 4 years ago

    successfully fixed everything, thank you to @palgramming and @pikamart for the feedback.

  • Abdulwahab Sani•125
    @aabsani
    Posted about 4 years ago

    Hi! Thanks a bunch i have changed the path by going up a level and it worked! And i have checked my repo link and it is working fine. Try again perhaps?

    And true... i inspected my grid since before uploading solution regarding the layout issue and i tried to fix it but couldn't figure out why. So it is unnecessary to specify height and width of my container?

    I will fix these errors and upload the new solution, cheers!

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted about 4 years ago

    Hey, great work on this one. The layout in desktop is good, but the mobile state and the responsiveness is not present.

    Regarding your query. You repo link does not work, fix that first. For the background-image, I tweak it since I can't see the repo, instead of using background-image: url(images/bg-pattern-quotation.svg); use background-image: url(../images/bg-pattern-quotation.svg);. I added ../ it means go up top by one level.

    One suggestion is that:

    • On the wrapper selector, remove the height:100vh, if you inspect your layout, you will see that the wrapper is not really capturing the whole grid, because it is only limited to what remaining viewport's height there is. Instead, use min-height: 100vh or you could just omit/remove the height property.

    The most important part is that , you must create a breakpoint, creating layouts so that your site will be responsive and mobile friendly. Right now those are missing, addressing it will be awesome.

    Still, good job on this one^

  • P
    Patrick•14,265
    @palgramming
    Posted about 4 years ago

    Two thing

    1. In desktop view the layout is not centered in the browser window
    2. The design will not transition small enough to get to mobile view

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

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

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