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

Testimonials grid section with CSS Flexbox and CSS Grid

Ryan O'Hanlon•140
@Ryan-OHanlon
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?

What I'm most proud of is that I'm starting to develop a better understanding of CSS Grid and that grids involve using a parent child relationship so you need to use two HTML container elements for CSS Grid to work.

If I could do something different this time, it would be to spend more time planning what the framework of the HTML elements to create CSS classes that would categorize the elements to make the stylesheet and html document readable on the backend.

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

The main challenges I encountered was how to use CSS Grid and CSS Flexbox together to handle margin and padding between the HTML elements.

When it came to grouping the portrait, the name and sub-title and having them organized I had to use a mix between CSS Grid and Flexbox to align the elements together. While this did place the elements together, I'm certain there is a better solution as dealing with the built-in margins and padding of paragraph elements to come closer together and being able to place them in a very specific spot makes designing the CSS rules very difficult.

.person {
    display: flex;
    align-items: center;
}

.personname p {
    margin: 0 0 5px 1rem;
}
What specific areas of your project would you like help with?

If there is one area I still would like help with each project is to know, when should I start limiting the size of objects for each project.

While I strive to match the mobile and desktop design pictures, I still struggle dealing with padding, margins and how to group HTML elements together and not take up the entire block. Sizing container elements so that it matches the challenge still elude me as I try to be a perfectionist.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Ryan O'Hanlon'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.