Simple Query

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

Why tables go stale

A hand-maintained overview is a snapshot: the moment you save it, it begins to age. Every new block, every status change in the existing set has to be entered by hand — and in day-to-day work that rarely happens in full. A query turns this around: it re-queries the existing set on every glance, so the view is always of right 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: when a block meets the criteria it appears; when it no longer does, it goes away.
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 maintain as a property, you can't query for.
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 truly current today, and how many show the state of a fortnight ago because nobody updated them? The answer decides whether an overview takes work off your hands or becomes one more thing you have to maintain.