Roberto Allende367 downloadsKanban that finally lives where your notes do.
Kanban that finally lives where your notes do.

I kept bouncing off every kanban plugin I tried. They lived in their own tab, cut off from the note I actually cared about — and honestly, the UI looked stuck in 1999. I could build something better. That's how I started Fancy Kanban. Here it is — you be the judge.
lanes: <field> in the board config; cards are arranged in a grid of columns × lanes, and dragging a card across a lane row updates both fields at onceobsidian-kanban boards over with one command; lanes become columns, cards and their notes are preserved, inline metadata (dates, tags) is stripped cleanlyFrom within Obsidian:
This inserts a fancy-kanban code block into your note (or opens one in a standalone view), pre-populated with a starter config and an empty table. From there, open the board setup panel to add or edit fields, columns, and workflow — no need to hand-edit the config block unless you want to.


If you have existing boards created with the Obsidian Kanban plugin, you can bring them into Fancy Kanban in one step:
.md file of an Obsidian Kanban board<original-name>-fk.md is created in the same folder and opened automaticallyThe original file is not modified. Each lane becomes a status column, card titles are preserved (dates, tags, block IDs, and wiki-links are stripped), and any multi-line card body becomes a description field on the card.
Add lanes: <field> to the board config to group cards by a second Select field. The board renders as a grid — column headers across the top, lane labels on the left. Dragging a card to a different lane row updates both the column and the lane field in the same operation.

```fancy-kanban
lanes: genre
```
Any Select field can be the swimlane field. You can also set it through the board settings panel — no hand-editing required.
Each board is a fenced code block — here's the board above, as it actually looks in the note's source:

```fancy-kanban
---
title: Website Relaunch
fields:
- name: title, type: Text, label: Title
- name: status, type: Select, options: todo|doing|done, label: Status, default: todo
- name: due, type: Date, label: Due
- name: priority, type: Select, options: low|medium|high, label: Priority
workflow: todo→doing, doing→done, doing→todo, done→doing
---
| _id | Status | Title | Due | Priority |
|--------|--------|------------------------|------------|----------|
| a1b2c3 | todo | Rewrite homepage copy | 2026-07-28 | high |
| d4e5f6 | todo | Source new photography | | medium |
| g7h8i9 | todo | Draft pricing page | 2026-08-02 | |
| j1k2l3 | doing | Build nav component | 2026-07-20 | high |
| m4n5o6 | doing | Migrate blog posts | | low |
| p7q8r9 | done | Set up staging env | 2026-07-10 | |
| s1t2u3 | done | Pick color palette | 2026-07-05 | medium |
```
Because it's a standard Markdown table under the hood, a board is still legible — as a table, without interactivity — in any Markdown viewer, even without the plugin.
If there's a gap you'd like prioritized, open an issue — this roadmap takes real usage and feedback into account.
Thanks to mgmeyers for obsidian-kanban, and to the Obsidian community for the feedback and reactions that helped shape this project's direction.
MIT — Copyright (c) 2026 Astuten.io Ltd