Skip to content
Submitted 7 months ago

Results summary component using HTML and CSS

accessibility, pure-css, web-components, webflow, animation
Caleb Abuul•320
@Caleb-Abuul
A solution to the Results summary component challenge
Preview (opens in new tab)Code (opens in new tab)

Solution retrospective

What are you most proud of, and what would you do differently next time?

I am most proud of the fact that I wrote the entire code for this challenge without seeking for external assistance. Which means I have significantly improved in my frontend development journey. I find the challenge quite simple enough. So, I planned on the design, and used only HTML5 and CSS to complete the challenge.

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

One of the challenges I encountered was that the content of one of the div was shrinking while the other remained the same as the screen size reduced. It turned out that I had used viewport values for its size i.e 60vw. So I changed it to percentage - 60%.

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

I am comfortable with my project right now, however, if there is anything I could do better I'd really love to know.

Code

Please log in to post a comment

Log in

Community feedback

  • P
    Huy Phan•3,430
    @huyphan2210

    Hi, @Caleb-Abuul

    I checked out your solution and I have some thoughts:

    • "Your Result" Section: It seems the height of this section shrinks on viewports 1024px wide or larger. This is due to an invalid grid-template-rows value in the media query. You can fix this by setting grid-template-rows: unset, which will help avoid the current setting of grid-template-rows: 40% 60% that's used for mobile viewports.
    • HTML and Body Sizing: Setting width: 100vw on body and html isn’t necessary since these are block-level elements that already fill the full width. Also, consider using min-height: 100vh instead of height: 100vh on body to ensure content expands appropriately on all screens.
    • Semantic HTML: You’re already using main and footer tags, which is great! To improve accessibility and structure further, try replacing generic divs with more descriptive tags like section or article where relevant.

    Hope this helps!

    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