Simple Query

Cmd+K finds a block. A query holds the finding in place: you describe once what you want to see — and from then on mium shows it to you on its own. Instead of a table you maintain, a filter line that thinks along with you.

Why tables go stale

A hand-maintained overview is a snapshot: the moment you save it, it starts to age. Every new block, every status change in the existing set has to be carried over by hand — and that is exactly what rarely happens in full day to day. A query turns this around: it queries the set afresh on every look, so the view is always of now.

5 rules for Simple Query

1. A query is a filter line, not a formula editor — type:meeting, status:open, autor:team-mut.
2. The view is live: if a block meets the criteria it appears; if it no longer meets them it disappears.
3. The same query renders as a list, a table or a board — you choose the view, the data stays one source.
4. Properties are the filter axis — what you don't keep as a property, you can't query.
5. A saved query lives as a block on a page, not as an external dashboard — it is part of the knowledge.

What a query looks like

{{query (and (property "type" "meeting")
              (property "status" "offen"))}}
;; Ansicht: Tabelle · Sortierung: zuletzt-geändert

Before and after — table vs Simple Query

An honest question

How many of your overviews are genuinely current today, and how many show the state from two weeks ago because nobody carried the changes over? The answer decides whether an overview takes work off your hands or is one more thing you have to maintain.