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

Responsive layout using CSS grid

P
krru09•200
@krru09
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 completed this project pretty fast! I think I'm getting the hang of css grid. I've come to appreciate grid-template-areas and grid-area properties, they make CSS grid way easier.

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

The fig file did not reveal a lot about the design requirements, I had to click around a lot to try and find certain design properties. For example, I had a lot of trouble trying to find the box shadow properties in the fig file. Also, I had some trouble with the quotation image and how to make it responsive with the different screen sizes.

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

I would like further help on how to make position: absolute and position: relative images responsive based on the screen size. I utilized multiple media queries and breaks as to where it should be based on the design, so it doesn't overflow out of the container it's attached to; but I'm sure there's probably an easier way. Please feel free to let me know!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sam•1,160
    @JustANipple
    Posted 5 months ago

    Hi @krru09, you've made a nice work, good job!

    For the image part, you could set a left and a right at 0px so you can set a margin auto to center it. Then just use transform: translateX to move it. This should keep it in the div through all the breakpoints.

    But there's another option. Instead of using the img tag, you could just use a background image for the div and position it at your needs, so it never overflows

    Check my solution if you want to see it live

    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