Simple Query
What if your overview were not a snapshot that ages from the moment you save it, but a view that keeps itself current — fed by the very blocks your team is writing anyway? Simple Query turns a filter line into a living dashboard and does away with the after-the-fact upkeep altogether.
- Without clean properties the query comes back empty — the upkeep shifts from the table to property discipline.
- Filters that are too broad return noise rather than a view; the criteria must be sharp.
- On very large sets the query must stay index-backed, or the speed suffers.
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
- A query is a filter line, not a formula editor — type:meeting, status:open, autor:team-mut.
- The view is live: when a block meets the criteria it appears; when it no longer does, it goes away.
- The same query renders as a list, a table or a board — you choose the view, the data stays one source.
- Properties are the filter axis — what you don't maintain as a property, you can't query for.
- 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ändertBefore and after — table vs. Simple Query
| Step | Hand-maintained table | Simple Query |
|---|---|---|
| Setting up | define columns, type in rows | type a filter line |
| Keeping current | enter every change by hand | keeps itself current |
| Switching the view | build a new table | switch list / table / board |
| Source of truth | the table (a copy) | the blocks themselves |
| Upkeep | ongoing | one time (the criteria) |
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.