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

Results summary component with basic HTML, CSS and Bootstrap

bootstrap
Nóra Lili Horváth•10
@NoraLili
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is my very first code challenge, and I had a lot of fun creating it while gaining valuable knowledge.

For this project, I used HTML, CSS, and Bootstrap to craft this visually appealing app component. While it's currently a static design, I'm thinking about adding JavaScript in the future to make it more dynamic and interactive.

  • I found it difficult to make the content responsive inside a div. When I changed the screen size, the content didn't stay inside the div, and the design didn't look right. I eventually fixed it, but it took more time than I thought.

  • I am uncertain of the layout, I was using absolute and relativ positions, if anyone knows an easier solution I'd love to hear it!

  • Also, if you have tips on using colors more easily, could you please share them? I used CSS classes for different colors, but it is just looks too coplicated like this.

I'd appresiate any feedback on my project, I would like to improve myself and learn how to make these projects more efficiently. :)

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • IryDev•1,580
    @IryDev
    Posted almost 2 years ago

    Hey @NoraLili, you make a great job on completing this challenge😄

    I have some suggestions in order to improve your code :

    • You use css class in order to apply color but you can avoid using css class you can use the selector summary-container:nth-child() in order to select your elements

    CSS :

    summary-container:nth-child(1){
    the color for the first container
    }
    
    summary-container:nth-child(2){
    the color for the second container
    }
    
    etc
    

    I hope you'll find this helpful, BTW your solution is pretty good😄

  • Azar•530
    @azr-arch
    Posted almost 2 years ago

    its good

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.