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

[React, TS, Recoil, Router, Formik + Yup, DND, vite] Kanban web app

react, react-router, recoil, styled-components, typescript
ErazorWhite•130
@ErazorWhite
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?

I'm most proud of effectively utilizing React Router (react-router-dom) to manage routing and modals within the application. By leveraging React Router's capabilities, I implemented modal dialogs that are seamlessly integrated into the app's routing system. This approach allows users to navigate directly to specific tasks or boards via URLs, enhancing the user experience and making the application more intuitive.

Additionally, I'm pleased with how I used Recoil for state management. Recoil provided a simple and efficient way to manage global state without the complexities of prop drilling or the overhead of more cumbersome state management libraries. It made the state management process straightforward and scalable.

Next time, I would aim to optimize the component structure earlier in the development process. Initially, I considered creating separate components for the sidebar and the mobile navigation modal. However, I realized that by using native CSS features, I could control this group of components more effectively. By applying CSS techniques like media queries and conditional rendering, I was able to create a single Sidebar component that adapts to both desktop and mobile views. This approach reduced code duplication and simplified maintenance.

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

One of the main challenges was designing a responsive sidebar that functions well on both desktop and mobile devices. My initial plan was to create two separate components:

Sidebar for desktop view. Mobile Navigation Modal for mobile view. However, this would have led to duplicated logic and styling inconsistencies. To overcome this challenge, I explored native CSS solutions that would allow a single component to adapt its layout based on the viewport.

By utilizing CSS media queries and flexbox layouts, I managed to create a single Sidebar component that:

Displays as a sidebar on larger screens. Transforms into a modal navigation menu on smaller screens. This approach not only streamlined the component architecture but also improved the user experience by providing consistent behavior across devices.

Another challenge was implementing modals using React Router. I wanted the modals (e.g., task details, edit forms) to be part of the routing system so that each modal could have its own URL. This allows users to share links to specific modals and enhances navigation.

To achieve this, I used React Router's useLocation hook and managed background locations to control the rendering of modals over the existing content.

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

State Management Best Practices: While Recoil has been effective, I'd appreciate feedback on best practices for scaling state management in larger applications. Are there patterns or techniques within Recoil (or alternative libraries) that could improve efficiency and maintainability?

Performance Optimization: Any suggestions on optimizing the performance of the drag-and-drop feature would be helpful. I'm curious if there are more efficient ways to implement this or if there are alternative libraries that might offer better performance.

Please feel free to provide any feedback or suggestions on these areas or any other parts of the project you think could be improved.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on ErazorWhite'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

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.