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

Painstackingly made Kanban app with React, TypeScript and Tailwind

laravel, typescript, sass/scss
Ilya Andreev•880
@NeoScripter
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 is my second attempt to create this application. The first time, I used Laravel and I made it as a full-stack app. It worked, but it was very clunky, unwieldy and had a lot of bugs. This time, I used completely different stack and this version of the app is so much better! This time, I used local storage and didn't make it a full-stack app but it's okay as it doesn't have to be, considering the use cases. I'm very proud of component structure, custom hook use and animation.

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

I encountered dozens of challenges and had to debug this app multiple times, starting from animation and state management up to optimizing CRUD operation on a state variable with super nested structure. The amount of experience I got from it is immense. It is truly remarkable how fast one can grow when they write all the code by themselves without AI. (I used it only when I was completely stuck but, honestly, AI is pretty bad at React code, at least in my experience).

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

Can anyone tell me how do you set up email notification on your app in Next.js in a straightforward way? It is not related to this project, but if anyone knowns, tell me please. I did a lot of research and found out that such a simple and straightfoward thing as sending an email (PHP does it natively and for free, by the way) is a whole mumba-dumba in Next.js. You need to spend several hours of your time setting everything up and paying third-parties some fees. Is there a really simple way that I didn't see online?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • maricastroc•560
    @maricastroc
    Posted 4 months ago

    Hello! I really liked the fact that you built a fullstack application and also implemented a language selection feature. Here are a few observations that might help:

    It might be interesting to show feedback toasts to the user during registration on the platform, as well as password validations; When clicking the 'add board' button in the boards area, nothing happens. I can only create a new board using the sidebar menu. I also noticed that the theme switch feature is currently not working.

    Other than that, I really liked your solution and the small design details. :D

    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