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

Result Summary Component using react and tailwind

accessibility, fetch, react, tailwind-css
P
Kamran Kiani•2,780
@kaamiik
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 successfully implementing a dynamic and responsive UI using React and Tailwind CSS. It was rewarding to see the components come together and function seamlessly across different devices. This was the third time did this challenge and I don't wanna do this again.

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

One of the main challenges was integrating Tailwind CSS with React components. Ensuring that styles were consistently applied across various components required careful attention to detail. I overcame this by thoroughly reading the Tailwind documentation and experimenting with different class combinations until I achieved the desired look. Additionally, fetching and handling JSON data asynchronously was initially tricky, but I managed it by leveraging React's useEffect and useState hooks to manage data fetching and state updates effectively.

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

I would appreciate help with optimizing the application's performance, particularly in terms of improving responsiveness. Additionally, any advice on best practices for structuring larger React applications would be valuable as I continue to scale this project and others in the future.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Prem Kumar•370
    @prem-kumart
    Posted 4 months ago

    The solution looks great. I could see some the good code practices. Helped me Improve my own 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 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