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

Grid layout section - Line-based placement with extended columns

bem
Mohammad-Moneer•120
@Mohammad-Moneer
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’m most proud of gaining more practical experience with the CSS Grid layout, particularly using line-based placement and extending items along grid lines. Additionally, I became more familiar with the BEM naming convention, which significantly helped in organizing CSS classes effectively.

Next time, I would explore using grid-template-areas as an alternative method for arranging items within the grid.

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

One of the challenges was maintaining the Grid layout structure across a range of screen sizes while ensuring that each testimonial article remained visually appealing and had an acceptable width to fit its content. To address this challenge, I implemented the following approach:

  1. Flexible Container Width: I set the width of the articles container (.testimonials) as a percentage, which allows it to adjust dynamically to different screen sizes: CSS .testimonials { width: 76.6%; }

  2. Adjusting Width for Medium Screens: For medium-sized screens where the content might feel too cramped, I increased the container width to make the articles more readable: CSS @media (max-width: 1160px) { .testimonials { width: 95%; } }

  3. Switching to Normal Flow for Small Screens: I carefully observed the behavior of the Grid layout as the screen size decreased to identify the point where it no longer fit well. Once I reached this breakpoint, I decided it would be better to switch to a normal block flow to maintain readability and usability: CSS @media (max-width: 800px) { .testimonials { display: block; width: 86%; } }

Hopefully, this approach ensures a responsive layout, maintains well-spaced content, and adapts the design seamlessly across various screen sizes.

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

I would like an evaluation of the design's responsiveness across multiple screen sizes. Additionally, I seek feedback on how well the layout performs and renders across different browsers.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Mohammad-Moneer's solution.

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.