Data tables
Linking docs and tables
Use a `doc_link` field to link rows to docs; backlinks show up automatically in the doc.
Why bind these two
A pain Notion users know well: a project has rich docs (meeting notes, specs, retros) and also lives as a row in a table (status, owner, deadline). Both halves need to stay in sync, usually manually.
Kition's answer is the doc_link field — a column in the table that points to a .md in the vault. The link is bidirectional: the table row knows about the doc, and the doc's backlinks pane lists every row that points to it.
Recommended pattern: a Projects table + a Projects/ folder
The cleanest workflow: one Projects table holds structured fields (status, owner, due, score), one Projects/ folder holds one .md per project for unstructured discussion. Add a doc_link field on the table called notes pointing at the corresponding file.
Click notes in the table → jump into the doc. The doc's backlinks pane auto-populates: "Linked from Projects → Launch v2". Deleting the row does not touch the doc; deleting the doc prompts you to clear the link.
The reverse direction: embed the table in the doc
doc_link goes table → doc. The reverse — doc → table — uses the ![[Tables/...]] embed syntax. Combined, you get a project-centric workspace: the project doc embeds a tasks view at the top (filtered to this project) and a contacts view at the bottom.
# Launch v2
> Status: `[[Projects#Launch v2]]` (linked row)
## Tasks
![[Tables/Tasks?project=Launch v2]]
## Related people
![[Tables/Contacts?project=Launch v2&view=gallery]]
## Notes from kickoff
...A few proven patterns
- CRM —
Contactstable +People/<name>.mdfor narrative notes, linked viadoc_link - Reading list —
Readingtable holds metadata (author, tag, score) +Reading/<title>.mdfor the take - Bug log —
Bugstable tracks repro state + aBugs/<id>.mdper P0 for the investigation log - Research papers —
Paperstable for BibTeX metadata + a doc per takeaway; userelationto thread related papers - Hiring pipeline —
Candidatestable for stage +Candidates/<name>.mdfor resume and interview notes
Sync and cleanup
- Rename the doc file —
doc_linkfollows (Kition watches vault filesystem events) - Move the doc to another folder — link survives
- Delete the doc — Kition prompts: "This leaves 3 broken links, clear them?"
- Scan for broken links via Settings → Diagnostics → "Find broken doc_links"
- In a team vault, link sync rides the vault protocol; conflicts resolve to the latest writer