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

Results Summary Component

react
Bunchydo•570
@Bunchydo
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 that I was able to structure the project using React components effectively and learned how to pass props (including images and class names) between components. I also used CSS techniques like aspect-ratio and flexbox to style dynamic content, which made the layout more responsive.

If I were to do this project again, I would plan the layout more carefully before coding, especially around spacing and alignment. Some styling issues took more time than expected because I didn't fully account for how CSS behaves in nested flex containers.

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

One major challenge was getting the layout spacing (gap) and circular shape (border-radius: 50%) to work properly. I learned that some CSS properties (like aspect-ratio) only work well when the parent container allows flexible height, and that gap only applies when display: flex or display: grid is used.

I overcame these issues by reviewing the parent container styles and adjusting the layout to support height expansion. I also broke components into smaller parts, which helped isolate bugs and made the code easier to maintain.

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

I'd like feedback on the following:

Am I using props in the most efficient and clean way, especially for passing styling classes and images?

Is my component structure clean and reusable, or should I restructure anything?

In terms of CSS: Are there better ways to manage layout spacing between elements (especially vertically), and how can I prevent layout issues like misaligned or non-scaling elements?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Bunchydo'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
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.