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

Kanban Task Manager with Nuxt 3,TRPC, Prisma, and Tailwindcss

nuxt, prisma, trpc, typescript, vee-validate
Kent Ntwari•100
@kentntwari
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 a great challenge to get myself familiar with Nuxt 3 and Trpc. It was quite a bit of fun and I've got to say that Trpc is amazing when it comes to end-to-end safety

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

Finding the proper way to compose Nuxt's useAsyncData into custom composables for the sake of being concise and hide the verbosity of useAsyncData was tricky and I ended up just using useAsyncData as is.

Styling the app was actually the major challenge I faced when working on this app and to be fair I'm still working on it because it's still not pretty enough. I had to sprinkle some javascript but I wish I could stick to CSS.

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

Nuxt can catch http responses and I wanted to rely on that especially when toggling between boards and only trigger a fetch when some change occurred. I didn't successfully find a way to make this happen and I guess this is more of a skill issue. I would like to get some insight on how to leverage Nuxt to make this happen and avoid extraneous http requests

Also, I really wanted to make only the boards area scrollable and everything else would just fit within the screen. I couldn't quite do that and it's quite frustrating. This caused the end result not to be as nice as it would've been because there's some excess scrollbars. Some insight on how to make this happen would be very appreciated

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 Kent Ntwari'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.