Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found

Submitted

Results Summary Component (HTML/CSS/JS)

@MellowTangelo

Desktop design screenshot for the Results summary component coding challenge

This is a solution for...

  • HTML
  • CSS
1newbie
View challenge

Design comparison


SolutionDesign

Solution retrospective


Hi all,

this is my second challenge on Frontend Mentor. I would like to hear your opinion on my solution.

I am interested in these topics in particular: 1.) Is my HTML ok, semantically? 2.) Is my CSS file structured correctly, and should it be divided in multiple CSS files instead? If yes, what's the common approach when dividing CSS files into smaller ones? 3.) Are there any other breakpoints that you can see on my web page?

Thanks in advance! :)

Community feedback

@MoggStephen

Posted

Hi there!

This is a great fluid responsive component.

To improve on your html semantically. You can use the section element to separate the result and the summary sections.

For a small component like this one css file should be fine! If you want to start separating css files you should look into using sass and sass partials! It can be easily setup within you projects with a live sass compiler.

Also class naming should be done using '-' and not '_'. This is called hyphen delimited string and is the standard convention for class naming in html and css.

Other than that its a great second solution!

Marked as helpful

0

@MellowTangelo

Posted

@MoggStephen Thank you for taking time to review my code. I appreciate your comments. Also, thaks for the tip about using "-". :)

0

@kimagin

Posted

Hello Pavle, I think you did a great job.

Regarding your question, you don't need to divide your CSS file into multiple files since most modern servers are minifying and compressing the CSS file on the server side. You can use Netlify or Vercel as your host which both offer this feature.

One common practice is to create all the media queries in a separate file and @import it in your style.css or main.css file. You can also inject CSS with javascript for the elements that you are dynamically creating. For bigger applications, you can use a framework such as React or VUE which gives you the opportunity to create individual components and write specific styling for each component in a separate file. For example, you can create a card component and use that multiple times over your project.

All that said, I think you are doing a great job, and can't wait to see your next project.

Marked as helpful

0

@MellowTangelo

Posted

@kimagin Thank you for taking time to review my code. I like the idea of separating media queries from a file. It can definitely improve readability of the code- I will try to use these useful tips in my next project. :)

1

Please log in to post a comment

Log in with GitHub
Discord logo

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