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

Results summary component

react
EmicJoykiller•270
@EmicJoykiller
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 most proud of how the component turned out visually and how smoothly it adapts to different screen sizes. Creating a visually engaging, responsive design with CSS variables and gradients was both rewarding and challenging, and I’m happy with how cohesive and intuitive the interface feels.

If I were to do something differently next time, I would approach component styling with styled-components or another CSS-in-JS solution to keep styling fully modular and encapsulated within each component. I would also consider enhancing the accessibility of the project, focusing on keyboard navigation and ARIA roles to ensure a more inclusive user experience.

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

A significant challenge was handling the file structure for SVG assets in the React environment, which required the assets folder to be placed directly inside the src directory to render correctly. Initially, this setup was causing errors, but restructuring the folder hierarchy resolved the issue.

Another challenge was designing a layout that’s visually appealing while also easy to navigate on mobile devices. To tackle this, I spent time researching responsive design patterns and used media queries extensively to ensure the UI looked polished on different devices. This also helped reinforce my understanding of CSS Flexbox and grid layouts.

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

Optimizing Performance for SVG Rendering: I’d love insights on how to best handle multiple SVG icons in React. Are there strategies to improve load times or alternatives to the approach I used?

Suggestions for Accessibility Enhancements: Accessibility is an area I want to improve in my work. Any feedback on making this component more accessible, especially for screen readers, would be appreciated.

Design and Usability Feedback: Lastly, I’d welcome suggestions on improving the UI design or usability features to make the component more intuitive and user-friendly for all users.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Leon Potgieter•290
    @leonp84
    Posted 7 months ago

    Hi, great design. An option for SVG or images with react is to place the files directly in the public folder (which is in the project root folder) during development. In your app.jsx - or wherever your main code is - you can then refrence them directly by URL path.

    So if image.jpg is in the public folder you can simply use:

    <img src="/image.jpg" alt="description" />

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub