Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 9 days ago

Results Summary Component

accessibility, react
Gustavo Gutiérrez•530
@gustavo2023
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What specific areas of your project would you like help with?
  • I refactored my single App component into ResultCard and Summary. Could this be improved further? For example, should each item in the summary list be its own SummaryItem component that receives data via props?

  • I used a JavaScript object (iconMap) to dynamically select the right icon for each summary category. Is this a good pattern in React, or is there a more common or efficient way to handle conditional rendering of assets?

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 Gustavo Gutiérrez'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