NotesDive
Supported Markdown task syntax
NotesDive collects task checkboxes from .md and .markdown files. Keep tasks as ordinary Markdown list items:
- [ ] Write the proposal
- [x] Send the proposal
Nested and numbered tasks work too. A checkbox marks a task complete; changing it in NotesDive updates the original file.
Available in the current download (0.10.0)
The current macOS download recognizes these optional fields on task lines:
| Field | Example | Meaning |
|---|---|---|
| Due date | due:2026-10-09 |
Deadline |
| Start date | start:2026-10-05 |
Earliest start date |
| Priority | priority:high |
high, medium, or low |
| Tag | #website |
Topic or project label |
Dates use YYYY-MM-DD. Invalid values remain visible as ordinary task text.
Inline task fields (0.10.0)
The current download also recognizes bracketed inline fields. This follows Dataview's inline field syntax; the field meanings below are NotesDive conventions.
- [ ] Write the proposal [assignee:: @mark] [start:: 2026-10-05] [due:: 2026-10-09] [priority:: high] [stage:: doing] #website
| Field | Accepted values | Meaning |
|---|---|---|
assignee |
One @name, such as @mark |
Person responsible |
start |
Date in YYYY-MM-DD |
Earliest start date |
due |
Date in YYYY-MM-DD |
Deadline |
priority |
urgent, high, normal, medium, low |
Importance; medium and normal have the same sorting rank |
stage |
backlog, todo, doing, review, blocked, done |
Workflow label |
| Tags | #name, for example #website |
Topic or project label; multiple tags are allowed |
When a task is checked, NotesDive displays its effective stage as done. If you uncheck it, its written open stage applies again; a written done on an unchecked task is treated as todo. A missing stage means todo for open tasks and done for checked tasks. The stage is currently a label: a drag-and-drop Kanban board and controls for assigning people or changing stages are planned, not part of the current download.
The older due:, start:, and priority: forms remain readable in the current download. Unknown fields and invalid values stay in the task text so your Markdown is never silently discarded.
The checkbox is part of GitHub Flavored Markdown. Bracketed fields are a Dataview convention rather than a universal Markdown standard. Other editors can still read the file as text, but they may not interpret the fields as task properties.