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

main results page using media query

Letícia Oliveira•300
@zapfish1
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

starting the project is one of the most challenging parts and i try to overcome it by trying, even if i feel overwhelmed and lost at first, my head clears out as i work on the project little by little!

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

i couldnt figure out how to stack '76 of 100' vertically. in the end i liked the side by side version, so i didn't bother with it... however, id love to know how i couldve done it

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Christopher Kola•260
    @Ckola99
    Posted about 1 year ago

    Hi there, first of all great work. I envy your colour and gradient skill there haha! I couldn’t get mine to be as accurate.

    To get the number 76 on a different line I used a span tag:

    <p class="result-score"> <span>76</span> of 100 </p>

    There after I styled it appropriately and placed a display block on the span tag so it could take up the whole line and push the other text to the next line like below :

    .result-score span { display: block; font-size: 5rem; font-weight: var(--fw-black); line-height: 1; color: white; }

    You’re welcome to check out my solution on my profile.

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub