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

Using displays flex and grid to present five historys

pure-css
Chame "Guigui-chan"•290
@Guilherme-Porto-Silva
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 last two times I completed chalanges for Frontend Mentor, I had gotten close to how the final layout looked at their screenshot but it was clearly not the same thing, wich was getting me kind of nervus, because I was felling like I couldn't get my products to be the way my clients ask. This time, though, at least I cannot notice a diference comparing the layouts in the two sizes presented at the beginig, and I even added a thirth size for tablets, with two columns. I was able to integrate Google Gemini into my work as well, to find out how those specific colors were called by the CSS language.

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

My media query had to change the start and the end of the grid columns to convert the layout from mobile to desktop size, that was a medieval torture for someone so used to using only flex. Google Gemini helped me in that as well, for I tryed to ask him what I was doing wrong and it warned me "The issue with the media query is that on screens wider than 1000px, the grid layout is set to display 5 columns, but there are only 4 main sections. This creates a gap in the layout where a fifth section would be.", so I could go there and fix my mestake without shooting in blind.

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

I had some trouble preventing the atribution div from placing itself on Kira's post. Got that off of my sholders using position relative in a very specific media query, but I fell like that was not the smartest way I could have done it, you know, as one of those who are aways trying to find cleaner and lighter paths to reach the same goals.

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 Chame "Guigui-chan"'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.