Simple Query
One filter line that becomes a living view — no table, no upkeep
- You write a Simple Query from property filters and get a view. ·· Success criterion: You phrase three filter queries, each showing the expected subset.
- You render the same query as a list, a table and a board. ·· Success criterion: You switch one query through all three views without rebuilding it.
- You explain why a query view stays current while a table goes stale. ·· Success criterion: You name the difference between snapshot and live query on an example of your own.
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
- A query is a filter line, not a formula editor — type:meeting, status:open, autor:team-mut.
- The view is live: if a block meets the criteria it appears; if it no longer meets them it disappears.
- 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 keep as a property, you can't query.
- 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 | Carry over every change | Keeps itself current |
| Switching view | Build a new table | Toggle list / table / board |
| Source of truth | The table (a copy) | The blocks themselves |
| Upkeep | Ongoing | One-off (the criteria) |
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.
- Take an overview you maintain by hand today — an open-tasks list or a status table. Decide on one property to carry the filter, such as status, and build a Simple Query that shows exactly those blocks. Then switch the view once through list, table and board.⏱ 5 min
💡 Start with a single filter of property plus value. If the view is empty, the blocks are missing the property — fill it in on two or three blocks, and the query populates on its own.
Model answer: A hand-maintained list of open tasks becomes a filter line that reads the property status with the value open. From then on the view shows every matching block and drops every completed one on its own. As a board it serves the standup, as a table the reporting — one source, three views, zero upkeep.
What sets a Simple Query apart from a hand-maintained table?
Search once, see for good.
One filter line, and your second brain shows the view — and keeps it current while you get on with other things. A companion that thinks along with you, not a table you feed.
Reserve your slot··free →