Tesria

Page properties

Page properties is a small two-column table of facts about a page, such as its status and owner, that a Page properties report can collect from many pages into one table.

On its own it is a tidy summary at the top of a page. Its real use is the report: give every project page, or meeting page, or incident page, the same properties and the same label, and a Page properties report elsewhere lists them all, one row per page, one column per property. Nobody has to keep that list up to date: it reads the pages each time.

Insert it

Type this

To get

/properties

A page properties table with Status and Owner rows

Type the command at the start of a line, or after a space, and press Enter. Or choose + on the toolbar, then Page properties. If you had text selected, the table takes its place.

Fill in the second column, and add rows for any other facts you want.

What it can hold

The first column names each property; the second holds its value. A value can be plain words, or a status, a person or a date. This is the page properties of this page, as a project page would have it:

Status

In progress

Owner

@Priya Natarajan

Due

Oct 14, 2026

Team

Launch

Keep the names the same on every page a report collects, such as always Owner and never sometimes Lead: each different name becomes a column of its own.

A report shows each value as plain text. A person comes through as their @name. A status or a date has no text of its own, so in the report it comes out empty; if the report should show it, type it as words.

One per page. A report reads only the first page properties on a page, and only its first two columns.

Changing it

It is an ordinary table, changed with the table controls: type in the cells, press Tab to move to the next one (in the last cell, Tab adds a row), and use the + between rows and the × on a row to add and delete rows. A row with nothing in its first column is left out of reports.

Good practice

  • Put it at the top of the page, where readers look for the facts.

  • Agree on the properties before the first few pages: a report is only as tidy as the pages it reads.

  • Make it part of a template, so every new page of that kind starts with the same properties. See Templates.


Applies to

Tesria 0.5 and later

Updated

September 24, 2026

Changes

Revised.