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

First react attempt

react, chakra-ui
José Mama•240
@codesByJose
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 have always thought learning how to use a framework will be so difficult. Im glad i used Chakra UI eaily. I learnt how to go about the media queries using the UI and it was surprisingly easy.

Also the react hooks, until this project i didnt really know how and when to use the useState how and even create custom hooks and how to utilize it knowingly, again this project has helped me to not just use but know its use case too.. i have done this project before using just html and cs, it didnt pan out so nicely especially with the media queries. Id like to think that i did it easier with this one.

i also didnt use the data.json previously when i did this project but this time around i was so confident about retrieving data from the json file, and the steps to doing that. I learnt that you can use the json file by directly importing it or calling it indirectly and so on and so forth. Basically i am excited for this one. Thanks

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

oh well... first i struggled with how to display the scores from the json how to use the data in there individually on the different elements. but im glad i did figure it out

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

at this point, all feedbacks are welcome. im open to improving this project. Thanks

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marzia Jalili•7,270
    @MarziaJalili
    Posted 6 months ago

    Well done buddy,

    Adjusment you could apply:

    • for a smoother color change add the line below to the button selector:
    button {
      transition: background-color: .2s;
      /* it makes sure that the transition will be delayed for 200 milliseconds */
    }
    

    Hope you find this helpful😎

    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 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