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

Developed Kanban using React, Typescript, Zustand and RadixUi

react, sass/scss, typescript, zustand, next
P
Vasilii•260
@mad-zephyr
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?

Creating a functional and attractive Kanban site: I managed to implement all the necessary functions while maintaining an aesthetic and user-friendly interface.

Successful integration of Zod and UseFormHook: Careful work on the integration of these libraries allowed us to ensure smooth work with forms and data validation.

Accessible Design: The use of Radix and extensive testing ensured that the site was accessible to users with disabilities.

Theme Switching: Implement the feature of switching between light and dark theme without compromising performance and usability.

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

Difficulties:

  • Zod and UseFormHook Integration: Both libraries are designed to work with forms, which required careful integration to ensure smooth operation.
  • Accessibility: Creating inclusive UI components using Radix required extensive testing and ensuring compliance with WCAG standards.
  • Themes: Implementation of switching between light and dark theme without compromising performance and usability.

Overcoming:

  • Zod and UseFormHook: A thorough study of the documentation and code examples of both libraries allowed us to find solutions for their effective integration. The use of hooks and function composition promoted modularity and code reuse.
  • Accessibility: Regular testing with accessibility tools and use of accessible Radix components ensured WCAG compliance.
  • Topics: Using CSS variables and media queries made it possible to change the color scheme of the entire site with minimal coding. Careful performance optimizations ensured smooth switching between themes.
What specific areas of your project would you like help with?

Enhancing the project:

  • Clarity and conciseness: Ensure your description is clear, concise, and easy to understand for a non-technical audience.
  • Highlighting key features: Emphasize the most impactful features and functionalities of your project.
  • Quantifying achievements: Use metrics and data whenever possible to demonstrate the success of your project.
  • Tailoring to the audience: Adapt your description to the specific interests and expectations of your target audience.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • alexander•1,300
    @alex931d
    Posted about 1 year ago

    Hey im sure you have all the functionality but on mobil the sidebar fills up 80% of my screen and the modals are not fitted for mobil view and to be honestly i don’t understand when i make a new kanban board that each column needs 4 or 5 characters it wouls be nice with some user feedback and more error handling to me it looks like you haven’t tested your page very much and i think you should work more on the accessibility especially when creating larger apps like the kanban app even if its just purely a frontend project :) hope it helps

    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