Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 years ago

[Challenge #3] Result Summary

Gastón Federico Nahuel Gómez•440
@Morfeo1997
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I redid this project from scratch because I now have more experience but I can't figure out why the container is stretched so much. Could someone explain to me why the height of the container stretches so much? The advice I got from the community helped me and any other advice is welcome.

Rehíce este proyecto desde cero debido a que ahora tengo mas experiencia aunque no logre entender porque se estira tanto el contenedor. Los consejos que me dejo la comunidad me ayudaron y cualquier otro consejo es bien recibido.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marcos Travaglini•6,210
    @Blackpachamame
    Posted about 2 years ago

    ¡Buen trabajo Gastón! por lo que estoy viendo el contenedor se estira porque le estas aplicando un height: 70vh; tanto a tu main como a ambos section. Eso genera que se estiren para cumplir con dicha propiedad.

    Por otro lado, te recomiendo que agregues un breakpoint cuando veas que en determinado ancho se "rompa" el diseño. Por ejemplo, en este caso, con un ancho de 500px el contenido ya empieza a quedar muy apretado, entonces, en lugar de hacer el media query para un máximo de 375px podes hacerlo para 500px directamente.

    Finalmente, te recomiendo que para tus próximos desafíos veas la posibilidad de usar variables, aunque sea solamente para los colores que te dan en la guía de estilos.

    ¡Saludos!

    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