Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Kanban board using React, TypeScript, and Tailwind CSS

react, redux-toolkit, typescript, tailwind-css
Inshal Haq•50
@inshal-haq
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?

Since this was the first big frontend project I have done, I am proud of the organization of my file structure, having a components, hooks, models, and store folder to organize the files. I am also proud of how well I matched the design!

Next time, I believe setting the correct typography and colors from the start would be helpful. Also I want to try creating a detailed component tree of each section, and building out the common UI components of the app before starting the full build. Also I would try different technologies, such as Jotai and Zustand, rather than Redux, for state management, and CSS modules instead of Tailwind CSS.

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

The first challenge I faced was how to start building such a huge project. I came to the idea of creating a component tree for the main sections of the app, and breaking them down everything into components and sub-components (example below).

  • Sidebar
    • Logo
    • BoardItem
    • LightSwitch

Another challenge I faced was creating a dropdown on a modal. For some reason, it would show behind the modal, so I had to programmatically define the element that the dropdown would anchor to and just hardcode values such as its position on the screen (if user resizes while dropdown is open, then this messes up its UI)

Another challenge was working with Redux-Toolkit. I created model types for the board, column, task and subtask, and I was receiving a serializable error. So I had to implement a toPlainObject() function to convert the data and also implement a serializeMiddleware() function

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

The last 2 challenges I mentioned above.

For the first challenge, I hard-coded the values to determine the position of the dropdown. So if there is a better way to do this, then that would be helpful. Or maybe I just have to rely on the default browser element and not create a custom dropdown on a modal. (this component is StatusDropdown.tsx in src/components/Task)

For the second challenge, which was working with Redux-Toolkit, I was just wondering if my redux store followed the best practice. Files like board-slice.ts and index.ts in src/store.

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 Inshal Haq'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 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.