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

Responsive sections using CSS grid

Katarzyna Kaźmierczak•260
@KasiaKaz14
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?

The CSS grid was the most complicated element in the whole project because I have never learnt this feature, so needed to hang out with it more. I am delighted I could deal with it, and arrange the sections in a proper way. The question what I could do differently is hard in this case because I don't know what I could do in another way. Maybe I could have finished project faster, and learnt more about the CSS grid.

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

I think that the answer is included in the first reply. The CSS grid was the biggest challenge for me. I haven't known it earlier, so could'nt arrange the grid as it was shown on the template. To overcome the problem I had to spend more time to learn how does it actually work, and try to apply it for the first time. I must admit I also need to use the Internet to find a solution for this question. After a half an hour I managed to resolve my problem and set all the sections according to the template.The key to the solution was grid-template-areas.

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

If someone could recommend me some good websites, apps or another source to learn more about CSS grid I will be grateful. Or maybe someone has a better way to set all elements properly

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ugo Francis•150
    @Vanfrankie7
    Posted 8 months ago

    Your result is great, the only issue is your card getting stuck at the top of the screen. After checking your code, i found out that maybe the cause is, you used align-items: center; instead of align-contents: center. it is flexbox that uses align-items to center a container. For Grid, it is justify-content and align-content. A shorthand for both of them in CSS Grid is place-items: center;

    if you finish the edits on your editor and push to github, wait a little moment and click on "Generate New Screenshot" in your frontendmentor's page to effect the changes you made in your code here.

    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

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