Skip to content

Page properties ​

Properties are typed key/value pairs above the page. They are the same thing as YAML frontmatter: on export they become real frontmatter, and on import real frontmatter becomes them. That is a total function rather than a best-effort one, and it is enforced by a rule about what a property may hold.

The types ​

Add a property, name it, and give it a type:

TypeHoldsExports as
texta stringa scalar
numbera numbera scalar
yes/noa booleantrue / false
datean ISO-8601 datea quoted string
lista flat list of scalarsa YAML sequence

The rule: frontmatter-shaped, always ​

A property value must be a scalar or a flat list of scalars. No nested objects, no object graphs. Dates are ISO-8601 strings.

That constraint is the reason properties can be promised to survive a round trip through Markdown. It is also why a database view can export as real Markdown pages with frontmatter, rather than as a dead CSV nobody can edit — every cell in the table is a property on the row's own page, and the page is an ordinary file.

What properties are used for ​

  • Frontmatter on export, and on import.
  • Columns, filters and grouping in a database view. A view selects pages and reads their properties; nothing lives inside the table.
  • The paper a page prints on. Six reserved names — page-size, page-orientation, page-margin, page-font, page-font-size, page-line-height — set the sheet, the margins and the typography for printing.

Names with a meaning ​

A few property names mean something to Notesflow as well as being ordinary frontmatter:

PropertyMeans
aliasesOther names the page answers to, for [[ links and unlinked mentions. Logseq's alias is read too. See links
ownerWho looks after the page
review_byWhen it should next be looked at. As the date nears, the page's header says Review due, and Review overdue once it has passed; a page with no date says nothing, rather than claiming to be fresh
templatetrue offers the page as a template
numbered, seriesOn a template, numbered: true gives each page started from it the next number in its series. See numbered records
numberA record's number in its series, given when the page is made
superseded_byThe record that replaced this one, as [[Title]]; the page's header says so
assistantfalse keeps this page, and every page under it, away from the assistant
timestampstrue shows when each line was written, as a log

Because they are ordinary properties, a list of stale pages is just a database view filtering on review_by, and an export carries all of them in frontmatter.

Block properties ​

Some properties belong to individual blocks rather than to the page, and none of them is set from the properties panel:

  • date — the day this item is placed on in the timeline. See the timeline.
  • timeline — pinned or hidden, curation within a day.

Both are set from the strip above the editor or the block menu, and export as an HTML-comment sidecar after the block, so a plain Markdown reader sees the text unchanged and ignores the comment.

  • A name, or a region — what block references point at, set with Make referenceable. They export in Obsidian's form, ^name and region comments.
  • A task's fields — due, start, priority, assignee, repeat and the rest, on a to-do. They are set in the task bar and export as Dataview's inline fields at the end of the line. See tasks.

Blocks and the op log are canonical. Markdown is a projection. Git is a target.