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

React based web application using redux, shadcn and tailwind.

react, redux, redux-toolkit, shadcn, tailwind-css
P
K Akash Rao•150
@kakashrao
A solution to the Kanban task management web app 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?

This was my first time working on a feature for switching between light and dark modes. It took me some time to explore the best ways to utilize the available resources effectively.

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

This is my first project built from scratch using React. I simultaneously read and worked on features, which helped me grasp the concepts more effectively. At times, I faced challenges with React libraries like React Hook Form and IndexedDB. To overcome these, I referred to the documentation and applied the concepts directly to the project.

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

As I come from an Angular background, I would greatly appreciate your feedback on the following areas:

Component Structure and Usage: Is my approach to handling components—such as their structure, usage of props, and implementation of hooks—well-organized, or are there areas where I could improve?

State Management Choices: Should Redux be used universally for data handling, or is it acceptable to use Context API selectively, as I did in one instance despite having a Redux store?

General Improvements: Any other suggestions for improvement—be it in terms of CSS, best practices, or other aspects—are more than welcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Karthik suryadevara•865
    @karthik2265
    Posted 6 months ago

    Hi akash,

    here are my thoughts/feedback on the solution:

    the functionality and design looks good. The responsiveness was also well handled. A small bug, I noticed that when a task is added with 0 subtasks (leaving the first subtask field empty when adding the task) it just renders 0 without any additional text to suggest that 0 means 0 subtasks.

    code

    • good idea to have draggable and droppable components, this way if we want to change the library in the future we only need to change in one place.
    • for the file structure, for me it makes sense to have the pages folder inside the src folder instead of inside the components folder and also note that it is better to follow a consistent naming pattern for files, I see that the files under the ui folder do not align with other component file naming structure which is pascal case. Also, the files inside pages folder could be organized better by placing each page file inside a folder and a dedicated folder inside the each page folder to holds the components used inside the page. Ex: home page would have structure like this home/index.tsx (holds the main page content), home/components (holds the components used in home page)
    • const listeners: Array<(state: State) => void> = [];used for dispatching actions and linked with setState, this could be simplified by using a useReducer hook provided by react.
    • redux for data handling or context with useEffect for client side data fetching/handling was used in the past but as of now many modern projects use libraries like tanstack query for data handling in the app on client side and another option is to use next.js or remix which handle data related updates on the server side with support for server rendered components. I liked working with remix and next.js, do try them out.

    overall the solution looks good, nicely done!

    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