Obsidian Workflow Setup |
\\n\\nThe features learned so far are like scattered tools in a toolbox—you know how to use a hammer or a screwdriver, but haven’t yet learned how to build a table.
\\n\\nThis chapter connects core features and plugins into 5 practical workflows, helping you upgrade from “knowing how to use tools” to “having a system.”
\\n\\n\\n\\n
Reading Notes Workflow
\\n\\nReading is the primary way of knowledge input. This workflow helps turn a book into a long-term, searchable, and linkable asset.
\\n\\nWorkflow Overview
\\n\\n- \\n
- Create a book home note: Use a template to quickly create a note and record the book’s metadata. \\n
- Record excerpts and annotations while reading: Use Callouts to distinguish between quoted text and personal thoughts. \\n
- Extract core concept notes: Turn important concepts from the book into atomic notes. \\n
- Establish links between concepts: Connect new concepts to your existing knowledge network. \\n
Book Home Template
\\n\\n---\\ntitle: "Book Title"\\nauthor: "Author Name"\\ntags:\\n - Reading\\n - Type/Technology\\nrating: 4\\ndate_started: 2026-05-01\\ndate_finished: 2026-05-20\\nstatus: Finished Reading\\n---\\n\\n\\nBody Structure
\\n\\nExample
\\n\\n# 《Book Title》\\n\\n## 3-Sentence Summary\\n\\n1. What is the book’s core idea?\\n\\n2. What is the most valuable insight?\\n\\n3. Who is it for, and what problem does it solve?\\n\\n## Core Concepts\\n\\n- []: One-sentence explanation\\n\\n- []: One-sentence explanation\\n\\n- []: One-sentence explanation\\n\\n## Excerpts & Annotations\\n\\n> [!quote] Excerpt\\n\\n> This is an important passage from the book.\\n\\nMy understanding: This passage means... It reminds me of [].\\n\\n> [!quote] Excerpt\\n\\n> Another important passage.\\n\\nMy understanding: This conflicts with Author A’s view because...\\n\\n## Action Checklist\\n\\n- Try applying Concept A\\n- Apply Concept B to my project\\n- Reread Chapter 3 and add more notes\\n\\n\\nDataview Aid: Book Dashboard
\\n\\nOn your homepage or a dedicated dashboard note, use Dataview to summarize all books:
\\n\\nExample
\\n\\n```dataview\\nTABLE author, rating, date_finished, status\\nFROM "Reading"\\nWHERE type = "book"\\nSORT date_finished DESC\\n\\n\\n\\n\\n\\n
Daily Workflow (Simplified GTD)
\\n\\nThis workflow doesn’t require formal GTD training—it only adopts the most practical parts.
\\n\\nDaily Process
\\n\\n- \\n
- Morning: Open today’s daily note and list 3 daily goals. \\n
- Daytime: Record ideas, add tasks, or update progress anytime in the daily note. \\n
- Evening: Review the day, check off completed tasks, and write a brief summary. \\n
Daily Note Template (Templater Version)
\\n\\nExample
\\n\\n---\\ntags: \\ncreated: <% tp.date.now("YYYY-MM-DD")%>\\n---\\n\\n# <% tp.date.now("YYYY-MM-DD dddd") %>\\n\\n## Today’s Goals\\n\\n- Goal 1\\n- Goal 2\\n- Goal 3\\n\\n## Notes & Ideas\\n\\n(Record ideas, inspirations, or temporary tasks anytime)\\n\\n## Today’s Summary\\n\\n### What Was Accomplished\\n\\n### Difficulties Encountered\\n\\n### One Key Focus for Tomorrow\\n\\n<% tp.date.tomorrow("YYYY-MM-DD dddd")%>\\n\\n\\nSummarize Incomplete Tasks with Dataview
\\n\\nPlace a Dataview query block on your homepage note to automatically collect all incomplete tasks from daily notes:
\\n\\nExample
\\n\\n```dataview\\nTASK\\nFROM "00-Diary"\\nWHERE !completed\\nSORT file.day DESC\\nLIMIT 20\\n\\n\\n\\nWeekly Review (Optional)
\\n\\nEvery Sunday, spend 15 minutes writing a weekly review note containing:
\\n\\nExample
\\n\\n# 2026-W21 Weekly Review\\n\\n## This Week’s Accomplishments\\n\\n- Completed X\\n- Progressed Y\\n\\n## Incomplete Tasks\\n\\n```dataview\\nTASK\\nFROM "00-Diary"\\nWHERE !completed AND file.day >= date(2026-05-18) AND file.day <= date(2026-05-24)\\n\\n## Next Week’s Focus\\n\\n1. Focus 1\\n2. Focus 2\\n\\n\\n\\n\\n
Learning Notes Workflow (Simplified Zettelkasten)
\\n\\nThis is a practical adaptation of the Zettelkasten methodology, tailored for technical professionals and students.
\\n\\nThree Types of Notes
\\n\\n| Type | \\nSource | \\nFeatures | \\nStorage Location | \\n
|---|---|---|---|
| Scratch Notes | \\nIdeas or inspirations that pop up anytime | \\nNo formatting required; quick capture | \\nDaily Note or inbox folder | \\n
| Literature Notes | \\nNotes taken while reading books, articles, or tutorials | \\nParaphrased in your own words, with original source cited | \\nResource folder for the relevant domain | \\n
| Permanent Notes | \\nRefined versions of scratch and literature notes | \\nAtomic, one concept per note, linked via bidirectional links | \\nScattered across the vault; discovered via links, not folders | \\n
Practical Steps
\\n\\n- \\n
- When learning something new, first record it in your daily note or temporary note (scratch note). \\n
- DuringOrganization, rewrite core concepts as independent notes (literature notes → permanent notes). \\n
- Add bidirectional links to each concept note, connecting it to existing knowledge. \\n
- Open the backlinks panel to check whether your new note is naturally referenced elsewhere. \\n
Concept Note Template
\\n\\nExample
\\n\\n---\\ntags:\\n - Concept\\n - Programming\\ncreated: 2026-05-21\\naliases:\\n - Concept Alias\\n---\\n\\n# Concept Name\\n\\n## One-Sentence Definition\\n\\nClearly define the concept in one sentence.\\n\\n## Detailed Explanation\\n\\nExplain the concept in your own words—avoid copying textbook content.\\n\\n## Why It Matters\\n\\nIn what scenarios is it useful? What problem does it solve?\\n\\n## Related Concepts\\n\\n- []: Prerequisite knowledge\\n- []: Further reading\\n- []: Contrasting or opposing concept\\n\\n## Code Example (Optional)\\n\\n```python\\n# A minimal runnable example\\n\\n\\n\\n\\n\\n\\nThe core idea of Zettelkasten is “write your own understanding,” not “copy others’ words.” If you onlyCopy-paste (Copy-paste meansCopy-pasteTransfer—Copy-paste porter =Copy-pasteTransfer worker) textbook content into Obsidian, you’re just aCopy-pasteTransfer worker—not truly internalizing knowledge.
\\n
\\n\\n
Writing Workflow
\\n\\nFrom idea to publication—everything happens inside Obsidian.
\\n\\nFour-Stage Workflow
\\n\\n| Stage | \\nNote Type | \\nTools | \\n
|---|---|---|
| Material Collection | \\nScratch notes, excerpt cards | \\nDaily Note + Quick Capture | \\n
| Outline Planning | \\nOutline note | \\nOutline panel + Canvas drag-and-drop | \\n
| Draft Writing | \\nDraft note | \\nEditor area + Focus Mode | \\n
| Publishing & Export | \\nFinal version | \\nExport PDF / Obsidian Publish / Pandoc to other formats | \\n
Material Collection Stage
\\n\\nWhenever you encounter content related to your writing topic during daily reading or thinking, record it immediately.
\\n\\nFor each writing project, create a “material pool” note and use Dataview to query content tagged with #Writing/Project Name.
Outline Planning Stage
\\n\\nCreate outline cards in Canvas and drag them to reorder. Use connections to indicate logical relationships.
\\n\\nAlternatively, write an outline note directly, using heading hierarchy to represent chapter structure, and use the outline panel for a global view.
\\n\\nDraft Writing Stage
\\n\\nPress Cmd+P → “Focus Mode” to hide all sidebars.
After writing each section, use %%comment%% (Obsidian’s comment syntax) below to mark revisions. These comments are visible only in edit mode and hidden in preview mode.
Publishing & Export
\\n\\n- \\n
- Export PDF: Use Obsidian’s built-in export feature. \\n
- Export Word/HTML: Install the Pandoc plugin to convert Markdown to various formats. \\n
- Build a Digital Garden: Use Obsidian Publish to publish your entire vault as a website. \\n
\\n\\n
Project Management Workflow
\\n\\nUse Obsidian to track progress across multiple projects—not as a replacement for Jira, but as a personal project dashboard.
\\n\\nProject Note Template
\\n\\nExample
\\n\\n---\\ntags:\\n - Project\\nstatus: In Progress\\ndeadline: 2026-06-15\\npriority: High\\n---\\n\\n# Project Name\\n\\n## Goal\\n\\nOne-sentence description of the desired outcome.\\n\\n## Key Milestones\\n\\n- Milestone 1: Specific deliverable — Deadline: 2026-05-30\\n- Milestone 2: Specific deliverable — Deadline: 2026-06-10\\n- Milestone 3: Specific deliverable — Deadline: 2026-06-15\\n\\n## In-Progress Tasks\\n\\n- Task 1\\n- Task 2\\n\\n## Project Notes\\n\\n- []\\n- []\\n\\n## Blockers\\n\\n(Record current issues blocking progress)\\n\\n\\nCreate a Project Dashboard with Dataview
\\n\\nExample
\\n\\n```dataview\\nTABLE deadline, priority, status\\nFROM "10-Projects"\\nWHERE status != "Archived"\\nSORT priority ASC, deadline ASC\\n\\n\\n\\nPlace all project notes on your homepage or dashboard note for a clear overview of overall progress.
\\n\\n\\n\\n
Homepage Design Suggestions
\\n\\nA well-designed homepage (Home Note) is the first interface you see every time you open Obsidian.
\\n\\nRecommended structure:
\\n\\nExample
\\n\\n# Welcome back ?\\n\\n## Quick Links\\n\\n- [[00-Journal/{{date}}|Today’s Diary]]\\n- []\\n- []\\n\\n## Current Projects\\n\\n```dataview\\nTABLE status, deadline\\nFROM "10-Projects"\\nWHERE status = "In Progress"\\n\\n## Incomplete Tasks\\n\\n```dataview\\nTASK\\nFROM "00-Diary"\\nWHERE !completed\\nLIMIT 10\\n\\n## Recently Updated Notes\\n\\n```dataview\\nTABLE file.mtime as "Last Modified"\\nFROM ""\\nSORT file.mtime DESC\\nLIMIT 5\\n\\n\\n\\n\\n\\n\\nThe homepage’s purpose is not “to look nice,” but “to be useful.” Put the information you most need to see every time you open Obsidian—such as today’s to-dos, ongoing projects, or recently modified notes—on your homepage. Keep refining it until it truly becomes your main entry point.
\\n
\\n\\n
Workflow Selection Recommendations
\\n\\nYou don’t need to adopt all five workflows at once. Build them progressively, following this priority:
\\n\\n| Phase | \\nStart With | \\nReason | \\n
|---|---|---|
| Week 1 | \\nDaily Workflow + Homepage | \\nEstablish the habit of opening Obsidian daily; other workflows naturally extend from this. | \\n
| Week 2 | \\nLearning Notes Workflow | \\nMost directly applicable if you’re currently learning new material. | \\n
| Month 1 | \\nReading Notes Workflow | \\nApply the template when starting your next book. | \\n
| As Needed | \\nWriting / Project Management Workflow | \\nBuild only when you have concrete writing or project tasks—avoid building empty frameworks in advance. | \\n
YouTip