Dataview

InkStone implements a server-side Dataview engine that executes TABLE and LIST queries from fenced ```dataview ``` blocks. Queries run at vault-load time — no client-side plugin needed.

TABLE query

```dataview
TABLE date, summary
FROM #documentation
SORT date DESC
LIMIT 3
```

Each row in the result corresponds to a vault note. The first column is always the note title (as a link) unless WITHOUT ID is used.

Column aliases

```dataview
TABLE date as "Published", summary as "Description"
FROM #inkstone
SORT date DESC
LIMIT 3
```

The as "Label" syntax renames a column header.

WITHOUT ID

```dataview
TABLE WITHOUT ID title, date
FROM #documentation
SORT date ASC
LIMIT 3
```

Suppresses the default "File" (title/link) first column.

LIST query

```dataview
LIST
FROM #inkstone
SORT date DESC
LIMIT 5
```

Renders as a <ul> of linked note titles.

LIST with extra field

```dataview
LIST summary
FROM #documentation
SORT date DESC
LIMIT 3
```

Appends — summary after each link.

FROM clause

Filter the source notes:

WHERE clause

Filter by any frontmatter field or computed property:

```dataview
TABLE date
FROM #inkstone
WHERE contains(tags, "documentation")
SORT date DESC
LIMIT 3
```

Supported operators

SORT clause

Multiple sort keys (comma-separated, applied right-to-left):

```dataview
TABLE date
FROM #documentation
SORT date DESC
LIMIT 3
```

LIMIT clause

```dataview
LIST
FROM #inkstone
SORT date DESC
LIMIT 5
```

Caps the result at N rows after sorting. Always add LIMIT when the result set could be large.

GROUP BY

Flattened groups (sub-table per group)

```dataview
TABLE date, summary
FROM #inkstone
GROUP BY file.folder
```

Renders a heading for each group, then a sub-table of its rows.

Collapsed groups using rows.field

```dataview
TABLE rows.file.link as "Page", rows.date as "Date"
FROM #inkstone
GROUP BY file.folder
```

When column expressions start with rows., InkStone renders one row per group, collecting values from all rows in that group.

Inline queries

Use `= expr` anywhere in note body to evaluate a field against the current note's frontmatter:

Published: `= date`
Author: `= author`
Tags: `= join(tags, ", ")`

this.field is an alias for the field name:

`= this.title`

Available fields

Every note exposes these in queries:

Expression functions

Private notes in queries

All vault notes — including those without website: true — are available to Dataview queries. This lets you use private notes as metadata sources or drafts while keeping them off the public site.

See also

• Tags — tag-based filtering in FROM/WHERE
• Publishing and Privacy — private notes as query sources
• Frontmatter Reference — all available frontmatter fields