A practical Obsidian vault template that combines PARA (Projects, Areas, Resources, Archive) with Zettelkasten thinking.
This template is for people who want to separate execution from thinking — without fragmenting their knowledge.
This is not a productivity experiment.
It is a long-term knowledge and action system.
- Projects = things with deadlines
- Areas = ongoing responsibilities
- Resources = reusable knowledge
- Archive = completed history
- Zettelkasten lives inside Resources
Build outcomes in Projects.
Extract knowledge into Resources.
Archive the rest.
Projects create outcomes.
Areas maintain responsibilities.
Resources build knowledge.
Archive preserves history.
PARA is infrastructure.
Zettelkasten is thinking.
PARA answers:
Where does this belong?
Zettelkasten answers:
How do I turn this into reusable knowledge?
They solve different problems.
Obsidian Vault/
├── 0. Inbox/
├── 1. Projects/
├── 2. Areas/
├── 3. Resources/
├── 4. Archive/
└── Templates/
There is no “Zettelkasten” folder.
Zettelkasten is implemented inside Resources.
Capture first.
Organize later.
If you don’t know what something is yet, it stays here.
Active efforts with a clear outcome.
Examples:
- Finish a novel draft
- Complete a programming course
- Launch a website
If there is no finish line, it is not a project.
When finished → move to Archive.
Projects produce results.
Ongoing responsibilities with no end date.
Examples:
- Programming
- Writing
- Health
- Finances
Areas are not storage folders.
They are control panels.
They may contain:
- Standards
- Checklists
- Links to active projects
- Links to knowledge hubs
Areas maintain quality over time.
Reusable knowledge and reference material.
This is where Zettelkasten notes live.
If something is:
- Reusable
- Not tied to one project
- Written in your own words
- Atomic
- Linkable
It belongs here.
Example structure:
3. Resources/
├── Programming/
├── Writing/
└── Finance/
Resources are assets.
Completed history.
Finished projects.
Old courses.
Inactive material.
You keep the record.
You remove the noise.
MOCs live inside Resources.
They are navigation layers.
They answer:
What do I know about this topic?
They do not store knowledge.
They link knowledge.
A note can appear in multiple MOCs. That is expected.
A course is a Project.
The knowledge extracted from it belongs in Resources.
flowchart TD
A[Start Course] --> B[Create Project Folder<br>1. Projects/Course Name]
B --> C[Create project file with tasks and due dates]
C --> D[Take Raw Notes Inside Project]
D --> E[Extract Atomic Notes]
E --> F{Reusable?}
F -- Yes --> G[Move to 3. Resources/Topic/]
F -- No --> H[Keep inside Project]
G --> I[Link inside MOCs]
I --> J[Knowledge Becomes Permanent]
J --> K[Finish Course]
H --> K
K --> L[Move Project to Archive]
- Take messy notes inside the Project.
- When an idea becomes clear, rewrite it as an atomic note.
- Move it to Resources.
- Link it in a MOC.
- When the course ends, archive the Project.
A course is temporary.
Knowledge is permanent.
You may include a root file like:
My Tasks.md
It does not store tasks.
It aggregates tasks dynamically (e.g., with Dataview).
Tasks live inside Projects and Areas.
The dashboard reduces friction during execution.
- Finished Projects → Archive
- Old courses → Archive
- Areas may evolve, but rarely move
- Resources grow deliberately
- MOCs evolve when needed
Do not over-organize early.
Let structure emerge from use.
Projects produce results.
Areas maintain standards.
Resources build knowledge.
Archive preserves history.
Clarity scales.
Confusion compounds.
This system is built for clarity.