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

Results summary component

sass/scss
ggsuha•40
@ggsuha
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I tried using the fonts provided in the starter files but couldn't successfully implement them. As an alternative, I imported fonts from Google Fonts. Another challenge I face is that since I only have free access, it becomes difficult to determine the exact values for font size, margin, and other properties.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ozzy-codes•130
    @Ozzy-codes
    Posted about 2 years ago

    Hi ggsuha, Congrats on completing this project!

    Sharing some suggestions to consider!

    I forked your repo and sent over a PR to address the footer laying on top of your summary card when examining your site on mobile view (375px width). You can see a screenshot of the issue on the PR . Suggested code was written to retain your use of the grid property. Forked repo - branch: adjust_crowding_grid_solution

    TL:DR - I've moved properties set on main one level up onto body

    Sizing elements:

    I recently got some feedback on the use of px’s in sizing elements and accessibility considerations and wish to share the same with you! It's generally recommended to avoid using px for sizing elements which can affect website responsiveness and accessibility. Why designers should move from px to rem...

    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