Why I Built It
I realized that I was relying too heavily on my unreliable memory. My digital life was a mess of disconnected files and forgotten tasks. I needed a "personal operating system" for my life—something that would turn chaos into a structured system. My goal was to stop just collecting information and start building genuine knowledge. I wanted a solution that combined the best productivity methodologies—PARA, GTD (Getting Things Done), and Zettelkasten—into a single, cohesive ecosystem within Obsidian.
Technical Challenges
The biggest hurdle was not just learning the syntax, but designing a system where different methodologies could coexist without friction.
Integration Complexity: Merging GTD’s action-oriented workflow with Zettelkasten’s knowledge-building structure required careful planning. I had to ensure that a "Project" note could easily link to "Resources" without breaking the logic of the system.
Dataview Logic: Configuring the Dataview plugin to automatically pull the right data for the dashboards was a challenge. Creating queries that accurately filtered tasks by priority, context (e.g., @home, @computer), and status required precise coding to ensure nothing fell through the cracks.
Template Architecture: Designing 14 distinct templates (from "Daily Note" to "Experiment" and "OKR") that were both comprehensive and easy to use required multiple iterations.
PARA Structure Implementation
I adopted the PARA method (Projects, Areas, Resources, Archives) as the backbone of the vault organization. This ensures every note has a dedicated home:
01_PROJECTS: This is where the action happens. It holds tasks with specific goals and deadlines, separated into "Active" and "Creative" sub-folders.
02_AREAS: These are the spheres of life requiring constant attention, such as Health, Finances, and Home.
03_RESOURCES: A place for knowledge, materials, and notes that I want to reference in the future.
04_ARCHIVE: The destination for everything completed or inactive, keeping the active workspace clean and uncluttered.
00_INBOX: I also added a dedicated Inbox as the single point of entry to remove decision fatigue when capturing new ideas.
Dataview Dashboard Setup
To avoid manual searching, I built a "Command Center" powered by the Dataview plugin. It includes six specific dashboards:
Main Dashboard: A high-level overview showing the Top 3 priorities of the day, quick actions, and stats.
Task Dashboard: Filters actions by priority and GTD contexts.
Habit Dashboard: Tracks daily rituals and streaks.
Learning Dashboard: Manages Learning Paths and skill matrices.
Library Dashboard: A virtual bookshelf for reading lists and book notes.
MOC (Map of Content): Visualizes how different dots connect across various domains.
Lessons Learned
Capture First, Organize Later: The most critical lesson was the importance of the 00_INBOX. Trying to categorize an idea the moment it strikes kills creativity. It's better to dump it in the Inbox and process it during a Weekly Review.
Modularity is Key: I learned that you don't need to use every feature at once. The system works best when it's modular—starting with simple notes and adding complexity (like OKRs or Experiments) only when needed.
Automation Saves Sanity: Using Dataview to generate views is superior to manually curating lists. It transforms Obsidian from a text editor into a dynamic database.
Link to product: https://toniaczlog.github.io/moj-drugi-mozg/
Top comments (0)