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

Responsive Results Summary Component with SCSS

sass/scss, bem
Rinzet•50
@Rinzet
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'm proud of how I implemented a clean and responsive layout using SCSS partials and mixins to keep the styles modular and maintainable. I paid attention to semantic HTML structure and made sure the design stayed consistent across different screen sizes. The use of reusable components and organized SCSS made the project easier to scale and maintain.

If I did this again, I would:

  • Dynamically load data from a local JSON file instead of hardcoding the values.
  • Experiment more with CSS Grid for layout refinement.
  • Focus earlier on organizing the file structure to avoid cleanup later.
What challenges did you encounter, and how did you overcome them?

One of the main challenges was structuring the layout in a way that remained responsive and visually balanced across both mobile and desktop views. I initially had trouble with centering and scaling the container, but I resolved it by using a combination of min-height: 100vh, margin: auto, and flexbox direction mixins for better responsiveness.

Another issue was organizing SCSS into partials and mixins without overcomplicating the structure. I overcame this by planning out a consistent naming convention and keeping mixins focused and reusable.

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

This was my first time using SCSS, so I’d really appreciate any feedback on how I structured my files—especially regarding mixins, partials, and maintainability.

I’m also looking for advice on the scalability of my SCSS setup and how to better structure styles for larger projects.

Additionally, I’d love tips on how to improve responsiveness, particularly for centering and scaling elements on very large screens.

If there are any best practices I’ve missed or ways to make the code cleaner or more efficient, I’m all ears!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Rinzet's solution.

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
  • Use cases

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