Skip to content

Productivity methods ​

Aurora doesn't enforce a workflow. It gives you pages, collections, live queries, links and properties, and you decide how to use them. This page shows how popular productivity methods map onto those primitives, so you can adopt the parts that work for you.

Getting Things Done (GTD) ​

David Allen's Getting Things Done is built around five steps: Capture → Clarify → Organise → Reflect → Engage.

Capture ​

Use Quick capture (⌘J, Ctrl+J on Windows and Linux) and your journal to capture. Quick captures land in the Inbox. Capture everything immediately, without deciding where it goes yet. See Inbox & capture.

Clarify ​

Open your Inbox and process each item:

  • Is it actionable? → Convert to a Task, assign a next action.
  • Does it need more than one step? → It's a Project — create a Page for it.
  • Is it reference material? → File it with the right type and tags.
  • Someday / maybe? → Tag someday and move on.
  • Trash? → Delete it.

Organise ​

GTD listIn Aurora
InboxThe built-in Inbox
Next actionsA collection with a query: page type Task, status equals Next action
ProjectsA collection with a query: page type Project, status equals Active
Waiting forA collection with a query: page type Task, status equals Waiting
Someday / maybeA collection with a query: tag someday
ReferenceAll other pages, filed by type
CalendarThe built-in Calendar, for tasks with due dates

Each list is a collection that fills itself from its query. Pages move between lists when you change their status or tags. See Collections & spaces.

Reflect ​

Use the built-in Weekly review template from the template library (/templates) to do your weekly sweep: empty the inbox, review projects, and plan next actions.

Engage ​

Your Next actions list, narrowed by a context tag (work, home, errands), gives you exactly what to do next and nothing more.

GTD starter setup

  1. Use the built-in Inbox for unprocessed captures.
  2. Create a task status called Next action (in addition to the defaults).
  3. Create a task status called Waiting.
  4. Use the tag someday for deferred items.
  5. Create collections for Next actions, Waiting for and Someday, and keep them in a space in the sidebar.

PARA ​

Tiago Forte's PARA method organises all information into four categories: Projects, Areas, Resources, Archives.

PARA categoryDefinitionIn Aurora
ProjectsThings with a deadline and end stateThe built-in Project type, or tag project
AreasOngoing responsibilities with no end dateCustom type Area, or top-level pages
ResourcesReference material on topics of interestPages, databases, bookmarks by topic
ArchivesCompleted or inactive itemsA tag archived or a dedicated collection

Setting up PARA ​

  1. Turn on the built-in Project type in Settings → Workspace → Page types, and create custom types Area and Resource (optional; Pages work fine). PARA's fourth bucket, Archive, is a tag rather than a type: tag anything dormant archived.
  2. Create four collections with queries, and keep them in a space in the sidebar:
    • Projects: page type Project
    • Areas: page type Area
    • Resources: page type Resource, or your reference bookmarks
    • Archives: tag archived
  3. Use your Inbox (see above) as the staging area before filing into PARA.

Projects vs Areas ​

The PARA distinction is important and easy to lose track of. A Project has a clear finish line ("Launch the new website"). An Area is an ongoing standard you maintain ("Health", "Finances", "Team management").

In Aurora, the built-in Project type has a Due date field. If a project has no due date, ask whether it is really an Area.

Moving to Archives ​

When a project completes, open it and tag it archived. It now shows up in Archives. To keep it out of your active Projects list, use a live query on your dashboard with page type Project and a status filter that leaves out finished projects. Nothing is deleted; it's all still searchable and linkable.

PARA + GTD

PARA organises where things live. GTD organises what to do next. They complement each other well — PARA gives you the filing structure, GTD gives you the action management.


Zettelkasten ​

The Zettelkasten method (German: "slip-box") is a note-taking system based on atomic notes, unique identifiers, and dense bi-directional linking. It was developed by sociologist Niklas Luhmann, who used it to write over 70 books and 400 articles.

Zettelkasten maps closely onto Aurora's built-in features.

The three note types ​

Zettelkasten note typeIn Aurora
Fleeting notesQuick captures and journal entries: raw, unprocessed thoughts
Literature notesA Page summarising a book, article, or talk (link to the source as a Bookmark)
Permanent notesAtomic Pages: one idea per page, written in your own words

The core practice ​

  1. Capture fleeting notes as they occur — quick capture or journal entry.
  2. Process them into literature notes (if from a source) or permanent notes (if your own insight).
  3. Link every permanent note to at least two related notes using @ links.
  4. Let structure emerge — don't pre-organise into folders. Structure comes from the links.

How Aurora supports Zettelkasten ​

Zettelkasten requirementAurora feature
Unique, permanent IDsEvery block and page has a permanent unique ID
Bi-directional linksBuilt-in backlinks on every page
Unlinked mentionsSurfaces notes that mention the current topic without linking
Link to specific passagesBlock references: link to a specific paragraph with Copy block reference
Visual overview of connectionsGraph view: see your whole slip-box as a graph
Folgezettel (sequence notes)Number your notes in the title (1a, 1a1, etc.) and link them in sequence
Tags for loose grouping#tags in the text, collected into each page's tags

A Zettelkasten workflow in Aurora ​

Step 1 — Capture fleeting thoughts

Press ⌘J (Ctrl+J on Windows and Linux) throughout the day. Don't worry about format. These are scratch notes.

Step 2 — Process into permanent notes

Each evening or during your weekly review, open your Inbox. For each fleeting note that contains a real insight:

  1. Create a new Page — one atomic idea only.
  2. Write it in your own words (not a copy-paste from the source).
  3. Give it a descriptive title, not a generic one. Not "Note about evolution" but "Natural selection operates on variation in reproductive success, not on individual organisms".
  4. Link it to at least two existing notes using @.

Step 3 — Follow the links

When writing a new note, search your existing notes and ask: "What does this connect to?" Add @ links. The graph view shows you which notes are central (many connections) and which are isolated.

Step 4 — Let structure emerge

After a few hundred notes, you'll notice clusters forming in the graph. These clusters are your real areas of interest. Create a Structure note — a page that links to and narrates the most important notes in a cluster. This is your Zettelkasten's table of contents, built bottom-up from the links.

Is Aurora better than Obsidian for Zettelkasten?

Obsidian is excellent for Zettelkasten. The main differences with Aurora are:

  • Aurora has block-level references (link to a specific paragraph, not just a page)
  • Aurora has structured properties and relations on every page
  • Aurora has real-time collaboration, useful if you maintain a shared knowledge base
  • Obsidian is built around plain Markdown files on disk. Aurora can keep a workspace in a folder on your computer too (see Sync), but if raw file access is central to how you work, Obsidian is the more direct fit

Other methods ​

Aurora is flexible enough to support most personal knowledge management approaches:

MethodCore ideaHow to use it
Johnny.DecimalNumbered hierarchy for reference filesNumber your page titles; use collections with a Title contains rule to group by prefix
Second Brain (Tiago Forte)Externalise thinking into a trusted systemCombine PARA with progressive summarisation: bold the key passages, then summarise them at the top of the page
Bullet JournalRapid logging, migration, reflectionUse journal entries for rapid logging; migrate open items to Tasks each week
MOC (Maps of Content)Index pages that link out to clusters of notesCreate dedicated pages that serve as curated entry points into a topic
Commonplace bookCollect quotes, passages, and ideas from readingUse Bookmark pages for sources and Pages for extracted quotes, linked back to the book

The common thread: Aurora provides atomic pages, flexible links, structured properties, and collections and live queries. Most productivity methods are specific patterns layered on top of exactly those primitives.

Aurora is in public beta and free while beta.