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

First Submission - Results Summary Component - HTML and CSS only

eosook•130
@eosook
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I'm a true beginner when it comes to HTML and CSS. My CSS code feels very messy and all over the place. Are there any tips that you could give me in order to improve on this or any glaring problems you see in my code. I appreciate any help I can get.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Brandon Smith•80
    @brsmit1993
    Posted over 1 year ago

    If you're looking to organize your CSS better the two best pieces of advice I could give would be 1. Learn sass as soon as you can. Once you're comfortable with CSS learning how to use SASS will save you tons of headaches when it comes to organizing CSS the second thing would be to look into naming /organizing methods like BEM. BEM even if not followed perfectly just understanding the theory behind why / how people follow it will likely be a big help as well.

    https://www.toptal.com/css/introduction-to-bem-methodology

    Marked as helpful
  • Bryan Li•3,530
    @Zy8712
    Posted over 1 year ago

    Your site looks pretty good. Main things I'd add/change:

    • center your component using flexbox instead of assigning margins to it. Right now you center you component using margin-top: 10vh. A better way of doing it would be to make the parent component center the box for you. In this case, the parent container is the body. So assigning something like this to your body should center it:
    body{
       display: flex;
       flex-direction: column;
       justify-content: center;
       align-items: center;
       height: 100vh;
    }
    
    • if you want to reduce the amount of lines in your css you should combine things like margin-top, margin-left, margin-right, and margin-bottom all under margin.
    • if you want to learn other ways of writing clean readable styling code, I suggest you to learn SASS/SCSS once you've mastered a bunch of the basics in css

    Hope you find this feedback useful 👍

    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

Oops! 😬

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

Log in with GitHub