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

Results summary component with flex-and semantic HTML

bem
P
Freddy Santana•190
@Creixz
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello friends!

I just finished a new project, I think I've done pretty well and I would like to please let me know if you have any suggestions.

At the moment I'm just practicing HTML and CSS.

Thank you very much.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted over 1 year ago

    Hi there

    This is overflowing my screen because you've used explicit widths throughout. Take these principles I share and I recommend you pause and refactor all earlier projects applying the same before moving on

    1. You don't need a section to wrap articles, they are distinct. Personally I wouldnt use articles for this as there is nothing to be gained from it and this content would never be syndicated across different sites/pages. If you only are separationg content for layout purposes, divs are fine.
    2. The scores like 76/100 are one paragraph not two.
    3. Decorative images like these icons should have empty alt.
    4. The b tag is deprecated. Did you mean to use strong?
    5. The attribution should be in a footer landmark outside of main.
    6. It's better for performance to link fonts in the html head instead of css imports.
    7. Don't use any heights or widths except for the icons and the circle around the overall score.
    8. Always use a modern css reset at the start of the styles in every project. Get into the habit now. Andy Bell has a good one you can look up and use.
    9. Instead of component widths use a single max width in rem on the component.
    10. Font size must never be in px
    11. The button should be full width (100%) and have no height either. Use padding.
    12. Media queries must be defined in rem or em not px so that it works for those who have a different text size too.
    13. I expect your media query is set at too small a value too. There will not be room for the large screen layout at 425px wide.
    14. Don't use absolute positioning for the footer attribution. Let it sit in the dom normally. Never choose arbitrary values to position elements.
  • Olaniyi Ezekiel•7,580
    @Ezekiel225
    Posted over 1 year ago

    Hello there 👋

    Good job on completing the challenge !

    Your project looks really good!

    I have a suggestion about your code that might interest you.

    There is an very useful browser extension called Perfect Pixel that allow you compare with the design image and thus see the exact dimensions. I recommend it to you.

    Consider changing the background-color of the body element and the div with theclass of card to hsl(0, 0%, 100%), then add a box-shadow to the section with the class of card_component.

    body {
      background-color: hsl(0, 0%, 100%);
    }
    
    .card_component {
      background-color: hsl(0, 0%, 100%);
      box-shadow: 2px 2px 20px 0 rgba(0, 0, 0, 0.1);
    }
    

    I hope this suggestion is useful for future projects.

    Keep up the excellent work and continue to challenge yourself with new projects. Your progress is impressive, and each project is a step forward in your front-end development journey! 🚀🌟.

    Other than that, great job!

    Happy coding.

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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