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

Kanban with Next.js

P
David Inoa•150
@davidinoa
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


Project Challenges:

  • What strategies do you recommend for optimizing the responsiveness of the app across different devices? I found it challenging to maintain a consistent layout and functionality.
  • Managing state across the app was complex, especially with dynamic task updates. How do you effectively manage state in a full-stack React application?

Code Quality:

  • I'm unsure about the scalability of my current folder structure as the app grows. Could you review my project's architecture and suggest improvements?

Best Practices:

  • When integrating tRPC with React Query, I followed the documentation but am curious if there are any best practices or patterns I should adopt for better error handling and data fetching?
  • Are there any best practices for using Tailwind CSS in a Next.js project to ensure styling remains consistent and manageable?

Performance Optimization:

  • I've noticed some performance issues when loading data from the database and rendering it on the frontend. What are some effective strategies for optimizing performance in a Next.js and Prisma app?

Security Concerns:

  • What security best practices should I consider for a full-stack application using Clerk for authentication? I'm particularly interested in securing API routes and protecting user data.

Testing and Validation:

  • I used Zod for form validation and schema definition. Are there any patterns or strategies for making the validation process more efficient and comprehensive?
  • How do you approach testing in a project like this? I'm looking for advice on setting up a testing suite that covers the frontend interactions and backend API calls.

User Experience (UX) Feedback:

  • Could you review the UX of the task creation and editing flow? I'm looking for ways to make it more intuitive and user-friendly.
  • I implemented a dark/light mode toggle and am curious about best practices for designing themes that are comfortable for users across different lighting conditions.
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 David Inoa'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.