Alexandria
PARA organizes information into four broad groups:
In Alexandria, the closest fit today is to make each PARA bucket a tag. Tags can
also define properties such as status:select, priority:select, or
review_date:date.
Collections and saved Queries are not available yet. Use tags plus Link DB Table dashboards as the current approximation.
Create one tag for each PARA bucket, then define the properties you want to see when you review that bucket.
status as select, priority as select, and due_date as date.status:select and review_date:date.topic:string and status:select.archived_on:date and reason:string.The property types available today are boolean, select, multi-select, date, number, money, and string.
When you add a new item, create it as a normal page and apply the PARA tag that matches how you want to review it.
Project and choose the
existing Project tag.status to active, priority to
high, and due_date to 2026-08-01.For an ongoing responsibility, create a page such as Health, add the
Area tag from the tags bar, then set status and review_date inline in
the property panel.
A note can have more than one tag, so a project can also be tagged with a topic, person, workflow state, or any other tag that helps you find it later.
Use a normal page as your home dashboard.
/) and choose Link DB Table.Each Link DB Table shows all notes with that tag and the properties defined by that tag. Open a tag page's View settings when you want to switch between the property table and the cover gallery.
Because saved Queries are not available yet, use separate tags such as Active Project, Waiting, or Someday if you need narrower dashboard sections.