English · 繁體中文

Card Table - Dated Tasks

A task-first card table. Inspired by the Kanban plugin's table mode view. Every task is a card, and these cards form a table. Features include unique time-filtering functions, multi-user collaboration, and one card layout that looks the same on desktop and phone.

[!IMPORTANT] Reminder: This plugin is still under active development and will change frequently over the next few months. Please back up your data/environment before using it. Bug reports and feedback are highly appreciated!

Notice: This project is entirely built by AI agents using Claude. The project developer has limited experience with programming languages.

From 1.6.1 cards are written with the same [key:: value] fields as the Tasks and Dataview plugins, so their queries see your cards' dates and repeats too.

• Time filters. Year, month, week, day, overdue and repeat are always on screen, and the four date tiles follow one date. No date pickers, no pop-up dialogs — ◀ ▶ reach any day in a few taps.
• Instant search. Type a title or some content under New card and the table filters as you type.
• Sections. A section is a colour and a status — name the red one Waiting and every card in it is waiting.
• Working together. Every card takes signed, timestamped comments, and every write is atomic, so two syncing devices never overwrite each other.
• Still plain text. Dates, assignees, pins, comments and repeats live in the note. Turn the plugin off and you still have a task list anyone can read.

If Card Table saves you time, you can buy me a coffee on Ko-fi.

[!WARNING] 1.6.1 is a big update that changes the note format. Sorry for the trouble. Cards are now written with Tasks / Dataview [key:: value] fields instead of emoji.

• Your old notes still work: the old syntax is still read, and a card switches to the new syntax only when it is changed.
• To switch everything at once: Settings → Note format → Convert everything to the new format (one click; each note is backed up in its own folder first).
• Update every device to 1.6.1: Card Table 1.6.0 and older cannot read the new syntax.
• The full old-vs-new table is in The text format.

If anything goes wrong with the conversion or the plugin, please email me at [email protected], or open a GitHub issue.

Installation

1. Settings → Community plugins → turn on community plugins.
2. Browse, search for Card Table - Dated Tasks, install and enable it.

Not listed yet? Download main.js, manifest.json and styles.css from the latest release into <your vault>/.obsidian/plugins/card-table/, then reload Obsidian and enable Card Table - Dated Tasks.

Getting started

1. Open a note and run Open with Card Table from the command palette, the ribbon icon or the tab's ⋯ menu. The note remembers the mode you last used and opens that way next time. For a note that has never been opened as a board, the ribbon icon asks first: open this note as a Card Table, or create a new one.
2. A brand new note gets five sections (## 1 … ## 5). Sections are shown as colours.
3. Type a title and some content under New card and press Shift + Enter. The card lands on the day, week or month the filter bar is showing.
4. Tap the circle to mark it done, the date to move it, ✎ to edit, 💬 to comment.

Contents

• Features
• Keyboard
• Settings
• The text format
• Card Table, Tasks and Kanban
• Design rules
• Support

Features

Time filters

• Linked tiles — year, month, week and day follow one date; step any of them and the others follow.
• Overdue and repeat — one tap each, next to the date tiles.
• Calendar — pick a day or a range when the tiles are not enough. Weeks can start on Monday, Sunday, today or the 1st.

Search

• Type to filter — the New card title and content boxes filter the table as you type.
• Frequent titles — reuse a title in one tap; a used title brings back its last section.

Cards

• Edit in place — Obsidian's Live Preview editor right in the card, saved as you type; to-dos inside a card can be ticked.
• Pinned, repeating, archived — a pinned table on top, [repeat:: every 2 weeks], archive before delete.
• Merge and export — combine several cards into one, or export the current view to PNG or PDF.

Sections

• Colour and status in one — name the red section Waiting and every card in it is waiting.
• Managed in place — rename, recolour, add or delete sections from the New card ⋯.

Working together

• Comments — signed and timestamped, kept with the card they are about.
• Assignees or solo — assign cards to people, or switch assignees off.
• Safe with sync — every write is atomic, so two devices never overwrite each other.

Phones and layout

• One layout everywhere — the same cards on desktop and phone; desktop is just wider.
• Narrow or wide on desktop; light and dark follow your Obsidian theme.

Plain text

• Tasks- and Dataview-friendly fields — [due:: …], [start:: …], [repeat:: …]; older notes keep working.
• English and 繁體中文.

Keyboard

Formatting keys are your own: editing a card uses whatever you have bound in Settings → Hotkeys, exactly like any other note — the card editor is Obsidian's editor, with Live Preview, undo and [[ suggestions.

Submitting works the same in the new card, the card editor and comments:

Settings

Grouped the same way as in the plugin; What's new at the top lists what every version added.

The text format

That is the whole storage format — everything the table shows comes from lines like these:

## 1

- [ ] [pin:: on] [Orders] [start:: 2026-09-11] [due:: 2026-09-14] #Alex
    Two boxes each, needs to arrive before Friday
    - [ ] Call the supplier
    [cm:: 2026-09-11 14:20|Alex] Quote came back, 8% up on last time
    [ed:: 2026-09-11 14:20]

- [x] [Field] [due:: 2026-09-08] [repeat:: every 2 weeks]
    Check the greening suspect tree again
    [done:: 2026-08-25]
    [ed:: 2026-09-08 08:30]

The first line is the card: pin, title, dates, repeat, assignee. Below it come the content (written exactly as you type it — no automatic bullets), repeat records, comments, and last of all the edit time. The lines the plugin writes itself have no bullet either.

Old and new syntax

• Lines the plugin writes ([done::], [cm::], [ed::]) have no - ; times always use a four-digit year and minutes.
• Other fields on the first line (for example [completion:: …] or [priority:: …] written by Tasks) are kept as they are.
• A card without a title keeps its first content line on the first line, so Kanban can still read it.

What about my old notes?

They keep working and change only when touched. A card switches to the new syntax only when you edit it, tick it or change its date; nothing else in the note is touched.

One-click conversion. Settings → Note format → Convert everything to the new format converts every note you have opened as a Card Table in one go. Each note's original text is first saved in the same folder (name backup-20260916-1420.md). Edit times are kept, lines outside cards are left alone, and running it a second time changes nothing.

Card Table 1.6.0 and older cannot read the new syntax, so update every device that opens these notes. If something looks wrong after converting, or you have any question, please email [email protected].

Card Table, Tasks and Kanban

Tasks and Dataview. Card Table writes due, start and repeat the way the Tasks plugin reads them in its Dataview format, and every [key:: value] field is visible to Dataview queries. Repeats are handled by Card Table itself (mark this time done), so let Card Table tick repeating cards.

Kanban. Card Table was inspired by the table view of the Kanban plugin — the same markdown lists, read as rows instead of lanes. It grew from there into a board built around dates and comments.

Can I use both? Yes. Card Table only takes over notes you open with it (it remembers each note), and it never switches a Kanban board over on its own; it also unloads cleanly when Kanban intercepts the same Obsidian method. Both read ## headings and - [ ] cards, so a Card Table note opens in Kanban too, but Kanban only understands its own @{date} dates — Card Table's [due:: …] fields show as plain text there.

Design rules

1. Every write is one atomic read-modify-write inside Vault.process, so a concurrent write (sync, another tab, the previous action) is never overwritten with a stale copy.
2. The view never writes its own copy back. All changes go through one writer.
3. A card is identified by its title and first content line. When two cards match, its position in its section is tried first (checked against the line and the content), then content, the whole line and the edit stamp. If nothing tells them apart, the plugin refuses to write rather than guess.
4. Writes touch the smallest number of lines possible. Ticking a checkbox changes that line and the edit time, not the file.

Support

• Bugs and ideas: GitHub issues, or email [email protected]
• Support development: Ko-fi

Licence

MIT