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

Product list Card using React, Tailwind and TypeScript

accessibility, react, tailwind-css, vite, typescript
P
Kamran Kiani•2,780
@kaamiik
A solution to the Product list with cart 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 am most proud of successfully completing this project using React for the second time, along with TypeScript to enforce type safety and improve code maintainability. It was rewarding to see my growth in understanding state management, particularly with the useState and useEffect hooks, as well as implementing forwardRef for component references. I also took the opportunity to enhance accessibility by adding aria-live announcements for screen readers, which I believe is an important aspect of web development. Next time, I would focus on improving my state management approach by utilizing the Context API from the beginning, rather than relying on prop drilling (I have updated my code with Context now). This would help streamline the data flow and make the code base cleaner and more maintainable. Additionally, I would explore more advanced features of Tailwind CSS to further enhance the styling and responsiveness of the application.

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

During this project, I faced several challenges, particularly in creating components and effectively using the useState hook to manage state. Additionally, integrating TypeScript into the project required careful attention to type definitions and ensuring type safety across components. Initially, I struggled with structuring my components in a way that promoted reusability while also ensuring that state was managed correctly across them. To overcome these challenges, I took the time to break down the application into smaller, manageable components, which helped clarify their responsibilities. I also revisited the React documentation and various tutorials to deepen my understanding of the useState hook and how to manage props effectively. By practicing prop delegation, I was able to pass data between components more efficiently (update: Instead of prop drilling I have updated my code with Context API).

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

I would appreciate feedback on several specific areas of my project. First and foremost, I am looking for insights into whether there are any issues with my state management or component structure. I want to ensure that my use of the useState hook is optimal and that my components are designed for maximum reusability and clarity. Additionally, I’d like feedback on how I’ve implemented TypeScript in the project, particularly whether my type definitions and type safety practices are effective and maintainable. Furthermore, I would like to receive feedback on the accessibility features I implemented, particularly the aria-live announcements for screen readers. It’s important to me that my application is accessible to all users, so any suggestions for improvement in this area would be valuable. Lastly, I am open to any general advice on how I can enhance my code quality, whether through better practices, performance optimizations, or improved styling techniques.

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 Kamran Kiani'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
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.