Document editor
Embedding a table in a doc
`![[Tables/projects]]` embeds a whole table or one view into the doc.
Why embed
Documents tell stories; tables track state. They each shine in different ways — but a weekly report often needs both the narrative ("what shipped this week") and the structured list ("here are the tasks").
Embedding renders the table’s live snapshot inside the doc. What you write is what readers see, always fresh, no copy-paste drift.
Syntax
![[Tables/projects]] # 整张表 / whole table
![[Tables/projects#active]] # 一个视图 / a single view
![[Tables/projects?status=todo]] # 过滤 / filtered inline
![[Tables/projects?limit=5&sort=-updated]] # 排序 + 限制 / sort + limit
![[Tables/projects.row:a7f2]] # 单行 / a single rowInline query parameters
?status=todo— single-field filter?status=todo,doing— multi-value (OR)?priority>=2— comparisons (>, >=, <, <=, !=)?sort=-updated— sort (prefix-for descending)?limit=10— cap rows?fields=name,status,owner— column projection
Real-world patterns
Weekly report: embed the "tasks done this week" view, always fresh, never stale.
RFC doc: append the "related ADRs" filtered view so context is one scroll away.
Daily note: embed "tasks due today" at the top — opening the doc is your todo list.
## 本周完成
![[Tables/tasks?status=done&updated>=-7d&fields=name,owner,closed_at]]
## 进行中
![[Tables/tasks?status=doing&owner=me&sort=-priority]]Editing inline
- Embeds are read-only by default — prevents accidental edits
Cmd/Ctrl + Eon the embed toggles inline editing (change fields, tick checkboxes)- Edits write straight back to the source table — embeds are views, not copies
- Deleting the doc never touches the table; deleting the table breaks the embed