Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

Testimonials Grid Section with CSS Grid

Siyam Ahmed•130
@Siyam1888
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 am realy happy that I could use CSS grid to bring the site to life.

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

I think the most challenging and tedious part is making the fonts and sizes as per the design. They seem to disturb me on all projects.

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

Could you please suggest me any better way to achieve the same results?

And, is there any easy or more efficient way to deal with the font-sizes, margin, padding etc. to make the site look similar to the provided design images?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Andrey•4,580
    @dar-ju
    Posted about 1 month ago

    Hi, Siyam Ahmed!

    Of course, you can do an identical layout. This technique is called Perfect Pixel. Download the PerfectPixel extension for Chrome. Open the design file jpg in it. Settings: x-0, y-0, scale-1, button "center layer horizontally", button lock - on, button invert - on.

    In Chrome, select the Mobile screen and set the screen resolution to the same as the image.

    About your work:

    • look at this section at a screen resolution over 2400px, it looks stretched and difficult to read. Make a container for the layout that limits the width. The maximum width of 1440-1920px is comfortable for reading.
    • you forgot the background image of the quotes in the purple block (I see you've already done it)
    • try to follow the logic of the blocks, if the right block is the largest, then on the tablet layout also make it large - the entire width of the screen
    • why did you leave empty alt for the images? These are not abstract avatars or background images, these are images of specific users and they are semantically important
    • pay attention that the section tag must have a h1-h6 header, if there is no header, then you should think about using another tag, for example div

    Otherwise, great work, good luck with your development!

    Marked as helpful

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