Kanban Task Management Web App w/ React, Redux, Tailwind CSS, dnd kit!
Solution retrospective
My first guru challenge on Frontend Mentor!
I really enjoyed building this app, it was rewarding and incredibly challenging for me! I ran into countless issues along the way, sometimes pulling my hair over them lol, but the frustration and the feeling of accomplishment that accompanies it tends to be what makes the journey interesting! I've learned a TON and I'll definitely be tackling more guru challenges in the near future!
What challenges did you encounter, and how did you overcome them?Too many challenges to name them all 😂. I implemented redux on my own for the first time, which I think was a great choice for this project, as it involved very complex and deeply nested state updates. It definitely is not the cleanest code, but the project took me several days already, that if I strived to make it super clean, it would take longer than I'd like. I also forgot about some Tailwind properties that could've made my CSS writing cleaner, but I'll take that lesson and apply it on my next project.
What specific areas of your project would you like help with?Any feedback is much appreciated !
Please log in to post a comment
Log in with GitHubCommunity feedback
- P@dar-ju
Hi Luqman (Luke)!
Very cool work, congratulations on finishing the guru task! You used localstorage - that's doubly cool!)
Please look at some points:
- theme change and panel hiding elements are located below the screen in height and you need to scroll the page to access them. The aside tag has a line
min-height: calc(100vh + 150px);What is it for? After all, there is enough space on the screen to place it at the bottom without scrolling. The best option would be to make an "All boards" block and a block with a lower part, make the parent block flex and space-between - the tiles are draggable and that's cool! But when moving to another task, without releasing the mouse button, the block disappears from the field of view and appears only when you release the button, this can mislead the user
- keyboard accessibility is not fully implemented, not all elements can be accessed
- semantically it would be correct to define lists as lists, there is a list in the menu and lists in tasks, it is better to use ul\li
- for some reason, 2 tasks are created for me when I click the Create tasks button
- why is the Subtask field required to fill?
I think these are small things that can be easily fixed, really great work!
Marked as helpful - theme change and panel hiding elements are located below the screen in height and you need to scroll the page to access them. The aside tag has a line
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