Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 11 months ago

Results summary component css and html

P
yuval nisim•440
@nisimi96
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 learning every day new thing can't lie its was so difficult but we manage to finish it

i added couple animation to desktop screen and some animation to the mobile screen so this is something you have to check out

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

position was one of my problem cause i have don't different positioning method and got stuck on the media views and couldn't make it work so i went through the position lessons again and had to understand the different between grid and flex

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

grids and flex to know better the using of both and know when i want to use one over the other

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sara Dunlop•450
    @Risclover
    Posted 11 months ago

    Hi! So in regards to using grid vs. flex, the more you get used to working with CSS, the more you'll have an instinct for which one to use. In general though, grid can be used for the overall presentation of the web page whilst flex box sets the layout within the components. In reality they are probably being used interchangeably by most developers.

    The name grid should give you a hint - generally it's most useful when you need an actual grid. Flexbox is useful for a lot of other positioning techniques (like aligning arbitrary numbers of items or such)

    (You can also use grid and flexbox together, eg. grid for main layout, and flexbox for positioning individual items inside your grid cells)

    EDIT: In regards to this project specifically, I would use grid for the 4 boxes on the right side (Reaction, Memory, etc) because it's a literal 1x4 grid.

    However, I would use flex for the elements inside of these boxes, specifically aligning them with align-items: center to make sure they're centered horizontally, and justify-content: space-between so that the icon and title are on one side and the number ratio is on the other.

    The left side of the app (the side with the blue background), I'd personally use flex for that as well - flex-direction: column to make the elements vertical instead of horizontal, and justify-content: center to make them centered.

    Let me know if you have any questions!

    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 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