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

Results Summary Component | ReactJs | CSS | Animations

react, animation
AnaCarolina•240
@AnaCarol2001
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 the CSS-only animation of this project. But, for next time, I would like to use a CSS framework and an animation library.

I'm also glad I discovered how to use the Context Hook to guarantee the correct heading levels and a reusable heading component through the React learn docs and an article from up your a11y.

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

The sequence animation was the biggest challenge of this project. To overcome it, I used the CSS variables and the calc function on the animation-delay property to make the sequence work.

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

Any tip about how to better structure a React project? Besides that, I would appreciate any feedback.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • dk•280
    @jenna1k
    Posted 10 months ago

    clean implementation and impressive animation!

    Using index.js files in the components and assets folders has a few benefits:

    • Cleaner imports: You can import components and assets directly from the folder name instead of specifying the index.js file. For example: import Button from '@components/Button'; instead of import Button from '@components/Button/Button';.
    • Easier refactoring: If you need to rename a component or asset, you only need to update the index.js file instead of changing the import statements throughout your codebase.
    • Consistent naming: Using index.js maintains a consistent naming convention across your project.
    • Encapsulation: The index.js file can be used to export only the necessary components or assets from the folder, providing a layer of encapsulation.
    Marked as helpful
  • Teodor Jenkler•4,040
    @TedJenkler
    Posted 10 months ago

    Nice animation really impressed, continue the great work

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.

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