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

My Testimonials Grid Section Solution

sass/scss
P
Jocelyne Teles•180
@JocelyneTeles98
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 had the opportunity of trying for the first time sass/scss pre-processor, and finding some tools on Internet to generate grids in order to have a help on understanding the positioning of the elements inside the grid.

The next time, I will try to search for tools first that maybe help me understand faster a new property that I'm exploring for the first time in CSS.

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

Grids are very challenging but at the same time less time consumer if you compare to the flexbox approach. I think, I just need to practice more to get the idea of positioning and sizing of grid items.

I had to find an old tool that I remembered from a previous work experience to generate the grid CSS code: Grid CSS Generator (I'm sharing 'cause I found it helpful to start :D)

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

If you have any tips about sass/scss or grids I will really appreciate it! ❤️

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Eugen•180
    @Fender60
    Posted 8 months ago

    Hey, good job. There are a few nuances that I saw: you used section tags nested in article tags, which from the point of view of the syntax may be, but article and section should have their own header and body. For this particular layout it is not very correct to use this approach, the article tag is enough. I may be wrong as I am just learning, but I rely on the information that I have studied, if I am wrong please correct me. Good luck.

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