Project: An Obsidian Productivity System

Build the mental model

An Obsidian vault turns the PARA-style structure from earlier lessons into an actual folder tree, not an idea you have to remember to apply by hand.

Eight top-level folders -- 00 Inbox, 01 Projects, 02 Areas, 03 Knowledge, 04 Research, 05 Learning, 06 Resources, 99 Archive -- carry numeric prefixes so the file explorer sorts them in a predictable order, in every operating system.

00 Inbox sits first because everything lands there before processing; 99 Archive sits last because finished material should be out of the way without being deleted.

This project also depends on linked notes: a Research note investigating a question should link directly to the Knowledge notes it draws on, and Obsidian's backlinks panel should show every note that references a given Knowledge page.

Markdown stays plain and consistent across every folder -- headings, bullet lists, and wiki-links -- because Obsidian's real value is a set of local, portable text files, not folder-specific formatting.

The best system is the one you maintain

A vault with perfect PARA structure and zero links is worse than a messier vault you actually open and update every day.

text

OBSIDIAN VAULT STRUCTURE
------------------------
MyVault/
  00 Inbox/      <- unsorted captures land here first
  01 Projects/   -- outcome-driven, multi-step work
  02 Areas/      -- ongoing responsibilities, no end date
  03 Knowledge/  -- refined, reusable notes
  04 Research/   -- source material for a question
  05 Learning/   -- active courses / skills in progress
  06 Resources/  -- reference material you did not write
  99 Archive/    <- finished material, out of the way

EXAMPLE CROSS-FOLDER LINK
  04 Research/api-rate-limits.md
      references [[Token Bucket Algorithm]]
  03 Knowledge/token-bucket-algorithm.md
      backlink: <- api-rate-limits.md

Connect it to a real scenario

Create the eight folders

Type each numeric prefix exactly as shown so the file explorer sorts them correctly: 00 Inbox, 01 Projects, 02 Areas, 03 Knowledge, 04 Research, 05 Learning, 06 Resources, 99 Archive.

Capture into 00 Inbox first

Drop every new, unsorted note into 00 Inbox, then move it once you know where it belongs -- a folder move never breaks an existing link.

Link Research notes to Knowledge

End each Research note with a short list of the Knowledge notes it draws on, written as wiki-links so the connection tracks in both directions.

Check the backlinks panel

Open the linked Knowledge note and confirm the Research note appears in its backlinks panel automatically.

Link Learning notes the same way

Link every Learning note back to the Knowledge notes it builds on, so revisiting a topic later surfaces everything connected to it.

Keep Markdown plain

Use a title, a few headings, and bullet lists in every note -- skip embeds, custom CSS, and plugins until the basic structure is actually in use.

Use it for two weeks before adding more

Once the folders exist and a handful of notes actually link to each other, stop adding structure and use the vault for two real weeks first.

Numeric prefixes turn folder order into something the file explorer enforces, not something you have to remember
A linked vault beats a merely organized one -- folders sort by purpose, links connect by meaning
Backlinks make a Knowledge note's usefulness visible without any extra work on that note

Try the working example

javascript

// Validates that a described vault contains every required top-level
// folder, in the correct numeric-prefix order. Real, runnable.

const REQUIRED_FOLDERS = [
  "00 Inbox",
  "01 Projects",
  "02 Areas",
  "03 Knowledge",
  "04 Research",
  "05 Learning",
  "06 Resources",
  "99 Archive",
];

function auditVault(folderNames) {
  const missing = REQUIRED_FOLDERS.filter((name) => !folderNames.includes(name));
  const presentCanonical = REQUIRED_FOLDERS.filter((name) => folderNames.includes(name));
  const presentInGivenOrder = folderNames.filter((name) => REQUIRED_FOLDERS.includes(name));
  const inOrder = presentCanonical.every((name, i) => name === presentInGivenOrder[i]);

  return {
    complete: missing.length === 0,
    inOrder,
    missing,
  };
}

const completeVault = [
  "00 Inbox", "01 Projects", "02 Areas", "03 Knowledge",
  "04 Research", "05 Learning", "06 Resources", "99 Archive",
];

const incompleteVault = [
  "00 Inbox", "02 Areas", "03 Knowledge", "05 Learning", "99 Archive",
];

console.log("Complete vault:", auditVault(completeVault));
console.log("Incomplete vault:", auditVault(incompleteVault));

You should see

The audit reports the complete vault correctly:
Complete vault: { complete: true, inOrder: true, missing: [] }
And it pinpoints exactly which folders are missing from the incomplete one:
Incomplete vault: { complete: false, inOrder: true, missing: [ '01 Projects', '04 Research', '06 Resources' ] }

5-minute try-it

Run auditVault with the actual folder list from your own vault (or one you're planning) and confirm complete and inOrder both report true. If either is false, fix the folder names or their order before adding any notes.

One important caution

Spending the first session perfecting folder names and numbering instead of writing a single real note

Filing every note away neatly but never adding a single link between them, leaving the vault organized but not actually connected

Obsidian Help: Internal links — Productivity Systems