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

result summary component with html and css

Isaac Lezama•50
@IsaacLezama
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi, I made the solution for this challenge but I'm not very good with media querys and responsive designs, so it would be really appreciated if you could make observations and comment some advice or resources, thank you all in advanced!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alin Costea•190
    @CosteaAlin93
    Posted about 2 years ago

    Hello Isaac!

    • it would help if you would wrap both the 'result' and 'summary' div into another one (let's put this div a class 'card'). Why? because, if you notice on the desktop screen, the white background is applied to the whole card, and the violet color only on the 'result', thus making that effect
    • on the responsive side; I always begin designing something 'mobile first', then adjust stuff based on higher resolutions
    • in this case, you could set flexbox; , flex-direction: column; on the 'card' div
    • and use a media query, for card, to become flex-direction: row; once the resolution is above 768px
    • the design overall is done, one little detail, on the 'summary' div, reduce the margin of the 'continue' button, so that it is aligned with the items above it.

    Try the above and let me know! Hope my review helps.

    Best wishes,

    Alin

    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