Give your pages structured fields. A Page Type is one label; properties are named values you attach to pages — a Status of "Active", a Priority of "High", a Due date, an Owner that links to a person page. Define a property once and it's available to every page; fill it in where it's relevant. Properties turn a pile of notes into something you can sort, filter, and reason about.
Properties set on a page show in a small strip just above the page title, each as a name — value chip you edit in place: type into a text or number field, pick a date, toggle a checkbox, choose from a select, or — for a page-link property — click the page to jump to it or the ✎ to point it somewhere else. The ✕ removes a property from the page; ＋ opens the Properties palette to add or manage them.
Open the Properties palette (the strip's ＋, or click any property name). + Add property takes a name and a type:
Definitions live in the document, so they travel with it. Values are stored on each page and are encrypted along with the page when you lock it — see Encryption and Privacy.
In the Properties palette, ✦ Fill with AI reads the page and suggests values for your properties — a Status it infers from the wording, a date it spots, the right Select option. You review each suggestion and accept the ones you want; nothing is written automatically. It runs on your local model (see Local AI), and it won't invent a Select option or link to a page that doesn't exist.
Properties are a lens on your whole wiki. In the Properties palette, ⊞ Collect by property… (or the ⊞ beside any value) filters the page list to every page sharing that value — "show me all the Active projects". A chip at the top of the list shows the filter and the count; ✕ clears it. Found a filter you'll want again? Click the ☆ on that chip to save it as a smart collection — a saved query that lives in your Collections tab as a ◎ row with a live count. Click it any time to re-run the filter against your pages as they are now. See Navigating.
Open the Graph (⌃⌘G) and the Lens… menu gains your properties. Pick a value to
spotlight the matching pages, or choose ◑ Colour by a property to paint every node by
its value, with a colour key in the corner — your map, read by Status or Priority at a glance. See
The Graph.
Properties round-trip through YAML frontmatter. Export a Markdown Page and its properties ride
along at the top between --- fences; import a Markdown file that carries frontmatter and
MojoPad creates the properties (inferring each type) and fills the values. So your structured fields
survive a trip through Obsidian, a static site, or a plain-text backup.