Block-embed dashboards
Dashboards built from real blocks — live, not from copies
Transcript
What if your dashboard were not a collection of copies that go stale the moment you paste them, but a window onto the real blocks — live, in sync both ways? Over the next few minutes you will hear how a block-embed dashboard does exactly that, without ever duplicating a thing.
A block reference gives every claim an address. An embed goes one step further — it shows the block itself in a second place, the same block, not an image of it. So you are not pulling a copy into the dashboard; you are opening another window onto a single truth.
That is where the difference between an embed and a copy lies. Copy a block and you have two truths that diverge from the next edit on. Embed it and there stays one truth, visible in two places. Change the block in the dashboard and it changes at its home too — and the other way round. That is transclusion: one piece of content, many windows.
The idea is not new. Ted Nelson described it in 1981 as the heart of Xanadu, and Douglas Engelbart sketched the living document as early as 1962. What was theory for so long is, in the block model, finally an everyday thing — and it solves the problem of diverging copies at the root, because there is only one block, so only one state.
A good dashboard mixes embeds with queries. Fixed blocks for what stays — a sprint goal, say, that lives in the planning doc and here gets only a second window. A query alongside it for what keeps changing, such as the open tasks of the current sprint. Together that makes an overview you never have to chase by hand, because it is fed by what your team is writing anyway.
One point asks for care: an embed binds visibility, not permission. Whoever sees the dashboard sees the embedded block. Before you share, check that every embed is meant for that audience. And never delete the source block to remove an embed — take out only the embed, the block stays at home.
The honest question at the end: how many of your dashboards show copied states that were already stale the moment they were pasted? The answer decides whether a dashboard shows you the truth or just a photo of yesterday. One block, right everywhere — your second brain keeps every view current, because it never duplicates a thing.
Block references give every claim an address. An embed goes one step further: it shows the block itself in a second place — the same block, not an image of it. That is how you build a dashboard from real content that never drifts apart, because it copies nothing.
An embed is not a copy
Copy a block and you have two truths that diverge from the next edit on. Embed it and there is still one truth, visible in two places. Change the block in the dashboard and it changes at its home too — and the other way round. That is transclusion: one piece of content, many windows.
{{embed ((6c1b9a2e-7d84-4f12-a3b9-0e5c1d7f2a48))}}
;; zeigt denselben Block — eine Quelle, hier nur ein weiteres Fenster5 rules for block-embed dashboards
- An embed is the block itself, not a snapshot — there is no second version to go stale.
- Edits sync both ways: the dashboard and the home are one and the same.
- Mix embeds with queries — fixed blocks for what matters, rules for what keeps changing.
- An embed shows the block's children too; choose the granularity deliberately.
- Never delete the source block to remove an embed — remove only the embed, the block stays at home.
A dashboard from embeds and a query
## Sprint-Dashboard
{{embed ((a8e2d710-4f3b-4c1a-9e2d-5b7c8a1f0e63))}} ;; Sprint-Ziel, lebt im Planungs-Doc
{{query (and (property "type" "task")
(property "sprint" "aktuell"))}} ;; offene Aufgaben, liveBefore and after — copy dashboard vs embed dashboard
| Property | Copy dashboard | Embed dashboard |
|---|---|---|
| Content | copies | the same blocks |
| Freshness | ages from the moment you paste | always live |
| Editing | local only, drifts | in sync, both ways |
| Source of truth | unclear (two states) | the block itself |
| Upkeep | chase it by hand | none |
An honest question
How many of your dashboards show copied states that were already stale the moment they were pasted? The answer decides whether a dashboard shows you the truth or just a photo of yesterday.
One block, right everywhere.
Build your dashboard from real blocks, not from copies — your second brain keeps every view current, because it never duplicates a thing. A partner that tends one truth, not a wall of stills.
Reserve your slot··free →