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

Results summary using HTML and CSS

Miriam Kilangi•70
@Miriam2245
A solution to the Results summary component 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 am so excited to present this solutuion to the community and am happy that i have finished it. i am so proud of how i was able to use linear gradient for the first time and get that look like the design given

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

The challenges i faced were paragraphs getting out of div and i overcame them by hiding the overflow. another challenge was on the circle about how to get the exact look like the given challenge where again the numbers were getting out of div but i overcame by using block display

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

I need more help on the challenges chat occur to paragraph due to some automatic CSS that are already found in the website. example the padding of the paragraphs. Again I am open for any comments and maybe what should I improve to be mere competent for the next project. Thank you!!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dylan Heslop•2,460
    @dylan-dot-c
    Posted over 1 year ago

    Good job here.

    It's not responsive for mobile devices tho...

    Sometimes it's recommended to use mobile first as it's easy to scale from small to large and not the other way around...

    In this case you would need media queries to help with that

    I've realized the div is not perfectly centered.

    You can use better naming conventions for your CSS classes as some are confusing and can be misleading.

    Mainly focus on responsive design, flex or grid for centering.

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