Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

html,css

Alejandro•430
@adelayglesiafleitas
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 believe if I do it again, I would do it better.

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

Designing the grid was my biggest challenge.

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

I would appreciate any help to improve the code.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Tom Roche•330
    @TomrocheDev
    Posted about 1 year ago

    Good take on this solution! The design looks really good and professional.

    You request on help with cleaning up your code: First of all, your code looks fine to me. You use the right tags, which makes your code structured. What I would avoid, is the over-use of classnames. Not all tags need a classname (in my opinion). The thing I also would avoid, is the long classnames like "container__section_header_div_name", "container__section_texto1" and "container__section_texto2". These long classnames make your code hard to read, and it also makes elements hard to target when you want to change something. Like, when I read your CSS, I have to puzzle my way out to find out which properties are assigned to which element.

    I would recommend to use short and declaritive classnames and try experimenting with targeting elements without classnames. This way you will learn how to target elements effectively without overusing classnames. A great resource for this is CSS Diner. https://flukeout.github.io/

    Hope this helps!

    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
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