Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

Kanban task management with Chakra-UI & Next.JS (ver. 1)

chakra-ui, next, react
Po-Cheng Yeh•190
@blp100
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


Before tackling this challenge, I intentionally opted for an easier one to take a breather and keep my momentum going. So, this time around, I made a bold decision to dive into the guru level challenge.

I decided to elevate my skills by embarking on the Kanban task management web app, aiming to demonstrate my frontend expertise. However, this undertaking extended over 25 days, nearly a month, ultimately nurturing immense gratitude for this transformative experience.

At the outset, my goal was to become better acquainted with Next.js' latest feature - the APP Router. Moreover, through this challenge, I acquired a understanding of employing dynamic routers, which I want to build a blog by my own. That's really useful experience for me.

Furthermore, navigating JSON data, an area relatively unexplored for me. The exercise of fetching data within the context of frontend development enriched my proficiency.

In the end, it's not truly an end. Upon completing this challenge, I've found myself pondering about my next steps. But as I reflect on this, I realize that there's so much more I can delve into and learn. Perhaps diving into React Three Fiber or exploring other avenues. Anticipation for what the future holds is building up within me.

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 Po-Cheng Yeh'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 1st-party linked stylesheets, and styles within <style> tags.

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.