SOP-BLOCK-EMBED-DASHBOARDS-1.0Rev. v1.0··2026-05-21

Block-embed dashboards

Dashboards built from real blocks — live, not from copies

PROCEDURE

1
Address the source block via a block reference — copy ((id)).
TOOLS
mium
DURATION10 sec
☐Checkpoint: The block address is on the clipboard.
2
On the dashboard page, paste {{embed ((id))}}.
TOOLS
Embed syntax
DURATION10 sec
☐Checkpoint: The real block appears in the dashboard.
3
Add a query for whatever keeps changing (open tasks, status).
MATERIALS
Query block
DURATION60 sec
☐Checkpoint: The dashboard shows fixed embeds plus a live list.
4
Before sharing, check that every embed is meant for the audience.
MATERIALS
Visibility check
DURATION30 sec
☐Checkpoint: No confidential block is visible by accident.

BACKGROUND

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 Fenster

5 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, live

Before 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 →