Build Your Second Brain's Foundation

Build a PARA-structured Obsidian vault with Templater-powered metadata templates.

Introduction

30 Second Summary

Your best ideas and most useful information are scattered across apps, documents, and conversations. Most of it ends up in places you will never find again.

In this project, you will build a structured Obsidian vault that organizes your notes using the PARA method, auto-populates metadata through templates, and connects ideas through links. Every note you create will be machine-readable and ready for AI tools to parse in future projects.

What You'll Build

You will hit a single hotkey, watch a perfectly structured note appear with today's date and metadata already filled in, then navigate your connected knowledge network through a visual graph that shows how your ideas relate to each other.

By the end of this project, you'll have:

  • A one-hotkey capture flow that creates a new note of any type (inbox, project, area, resource) with structured metadata auto-populated by Templater.
  • A Map of Content that surfaces related notes across folders so you can navigate your vault by meaning, not just by folder.
  • A connected knowledge graph visible in Obsidian's graph view, where every note links to the ideas it builds on.
  • A consistent YAML frontmatter schema across every note in your vault that AI tools can query and process programmatically.
  • Secret Mission: Build a Daily Note template with a conditional weekly review checklist that only appears on Fridays.

Are there any prerequisites?

You need Obsidian installed on your machine before starting. No prior experience with plugins or YAML is required.

Before We Start

Before we dive in, let's lock in what you're about to build and why it matters. Committing to your specific use case now ensures every decision in the vault serves your actual needs.

Set Up the Vault Structure and Templater

Every note you create in this project needs a clear home. The PARA method organizes your vault into folders based on actionability: things you're actively working on, things you're responsible for, things you're learning from, and things you're done with.

In this step, you'll create that folder structure inside a new Obsidian vault and install Templater, the plugin that will power your templates in later steps.

In this step, get ready to:
  • Create a new Obsidian vault with PARA folders.
  • Install and configure the Templater plugin.
  • Verify the setup works with a test command.
Create the PARA folder structure

A vault is just a folder on your filesystem where Obsidian stores your notes as plain Markdown files. You need a fresh vault to build your Second Brain foundation in.

  • Open Obsidian. If you see the vault selector screen, skip to the next bullet. If you already have a vault open, click the vault icon in the bottom-left corner to open the vault switcher.
  • Click Create to the right of Create new vault.
  • In Vault name, type Second Brain.
  • Click Browse and choose a location you'll remember (your home folder or Documents works well).
  • Click Create.

Obsidian opens your new empty vault. You should see a blank workspace with the file explorer panel on the left.

Now create the six PARA folders. Each folder will hold a different category of notes.

  • In the left sidebar, right-click in the file explorer panel and select New folder.
  • Name the folder 00 Inbox and press Enter.
  • Repeat this process to create five more folders: 01 Projects, 02 Areas, 03 Resources, 04 Archive, and Templates.

Your file explorer should now show all six folders listed in alphabetical order.

Why number prefixes?

Obsidian sorts folders alphabetically and does not support manual reordering. The 00, 01, etc. prefixes pin your most active folders at the top so you always see Inbox first and Archive last.

The Templates folder has no number because it is a utility folder, not a PARA category. It sorts to the bottom naturally.

Don't see the file explorer?

If the left sidebar is collapsed, click the sidebar toggle icon in the top-left corner of the Obsidian window, or press Ctrl+Shift+E to open the file explorer.

Help me find the file explorer panel in Obsidian.

Install and configure Templater

Templater is a community plugin that lets you define templates with dynamic content like auto-populated dates and cursor placement. You need it installed before you can build any templates.

  • Open Settings by clicking the gear icon in the bottom-left corner of Obsidian.
  • In the left sidebar of the Settings panel, click Community plugins.
  • Click Turn on community plugins to disable Restricted Mode.
  • Click Browse to open the community plugin directory.
  • In the search box, type Templater.
  • Select the result by SilentVoid13.
  • Click Install.
  • Click Enable.

Templater is now active. You need to point it at your Templates folder so it knows where to find template files.

  • Close the plugin browser by pressing the X in the top-right corner of the browser panel.
  • In the Settings sidebar, scroll down to Templater under the Community plugins section.
  • Click Templater to open its settings.
  • Find the Template folder location field and type Templates.
  • Leave all other settings at their defaults.
  • Close Settings by pressing Esc or clicking the X.

What does Template folder location do?

This setting tells Templater which folder contains your template files. When you later run a Templater command, it scans only this folder and presents the files inside as available templates.

Don't see Templater in the settings sidebar?

Make sure you clicked Enable after installing. Disabled plugins do not appear in the settings sidebar. Go back to Community plugins and toggle Templater on under Installed plugins.

Help me enable Templater in Obsidian.

Verify the setup

Before moving on, confirm that Templater can see your Templates folder and is ready to use.

  • Open Settings again and navigate to the Templater section.
  • Confirm that Template folder location shows Templates.
  • Close Settings.
  • Right-click in the 00 Inbox folder and select New note. Name it Test.

Before you run the next command, what do you expect to see? You have no template files yet.

  • Open the command palette by pressing Ctrl+P.
  • Type Templater into the search field.
  • Confirm you see the command Templater: Insert Template in the results list.

The command appears but shows no templates yet. That is expected because the Templates folder is empty. This confirms Templater is installed, enabled, and pointing at the right folder.

  • Press Esc to close the command palette.
  • Right-click the Test note in the file explorer and select Delete.
  • Confirm deletion when prompted.

Don't see the Templater command?

If the command palette does not show any Templater commands, the plugin is not enabled. Open Settings, click Community plugins, and check that the toggle next to Templater is turned on.

Why don't I see Templater commands in the palette?

Your vault skeleton is ready. Next up, you'll build your first template and capture a real note with auto-populated metadata.

Build and Test the Inbox Template

Your vault structure is in place and Templater is configured. Now you need a way to capture notes that automatically stamps them with structured, machine-readable metadata.

The Inbox template is the simplest note type in the PARA method. It gives you an immediate working capture flow that proves the YAML frontmatter schema auto-populates correctly before you build the more complex templates.

In this step, get ready to:
  • Create the Inbox Note template with a universal YAML schema.
  • Capture your first real note using the template.
  • Verify the schema fields are auto-populated in Obsidian's Properties view.
Create the Inbox Note template

Every note in your Second Brain will carry six universal fields: type, status, created, modified, summary, and tags. The Inbox template defines these fields using Templater syntax so they auto-populate when you create a new note.

  • In the Templates folder in the file explorer sidebar, right-click and select New note.
  • Rename the file to Inbox Note (Obsidian adds the .md extension automatically).
  • Paste the following template content into the file:
<% "---" %>
type: inbox
status: inbox
created: <% tp.date.now("YYYY-MM-DD") %>
modified: <% tp.date.now("YYYY-MM-DD") %>
summary: <% tp.file.cursor(1) %>
tags: 
<% "---" %>

<% tp.file.cursor(2) %>

What does this template do?

The <% "---" %> syntax outputs a literal --- delimiter when the template is applied. This escaping prevents Obsidian from trying to parse the template file's own frontmatter (which would fail because of the Templater syntax inside).

The tp.date.now("YYYY-MM-DD") calls auto-populate today's date in both the created and modified fields. The tp.file.cursor(1) places your cursor directly in the summary field so you can start typing immediately. Pressing the cursor-jump hotkey moves you to tp.file.cursor(2) in the note body.

  • Save Inbox Note.md.
  • Confirm the file appears in the Templates folder in the sidebar.

Don't see the file in Templates?

Make sure you created the file inside the Templates folder, not at the vault root. Right-click the Templates folder in the file explorer and select New note to guarantee it lands in the right place.

Help me troubleshoot my template file location

✔️ Awesome, I've got everything!

Great. Double check you have saved Inbox Note.md before moving on.

ⓧ I'd like to double check the full code

Your Templates/Inbox Note.md should contain exactly this:

<% "---" %>
type: inbox
status: inbox
created: <% tp.date.now("YYYY-MM-DD") %>
modified: <% tp.date.now("YYYY-MM-DD") %>
summary: <% tp.file.cursor(1) %>
tags: 
<% "---" %>

<% tp.file.cursor(2) %>
Capture your first note

Time to put the template to work. You will create a real note from your Inbox template to see the schema populate live.

  • Open the command palette by pressing Cmd+P (macOS) or Ctrl+P (Linux/Windows).
  • Type Templater: Create new note from template and select it.
  • Select Inbox Note from the template list.
  • Name the note something real from your day (e.g., Meeting notes from standup or Article idea for blog).
  • Your cursor lands in the summary field. Type a one-line description of the note.
  • Add a tag in the tags field (e.g., work or idea).
  • Write a few lines in the note body below the frontmatter.

Why use something real?

A Second Brain only works when it holds real thoughts. Starting with genuine content now means you already have useful notes when you finish this project, instead of test data you will delete later.

Verify the schema

Before you move on, confirm that all six universal fields populated correctly and that Obsidian recognises them as structured properties.

  • Switch to Reading View by pressing Cmd+E (macOS) or Ctrl+E (Linux/Windows).
  • Confirm the frontmatter rendered correctly with no raw Templater syntax visible.
  • Switch back to Live Preview by pressing Cmd+E (macOS) or Ctrl+E (Linux/Windows) again.

What do you expect to see when you open the Properties view? Think about which fields should have today's date and which ones should have the values you typed.

  • Open the Properties view by pressing Cmd+; (macOS) or Ctrl+; (Linux/Windows).

You should see all six fields listed: type set to inbox, status set to inbox, created and modified showing today's date, summary showing the text you typed, and tags showing the tag you added.

Seeing raw Templater syntax instead of dates?

This means Templater did not process the template when the note was created. Make sure you used the Templater: Create new note from template command (not Obsidian's built-in New note button). The built-in button creates blank notes without running Templater.

Also confirm that Templater's Template folder location is set to Templates in Settings > Templater.

Help me troubleshoot raw Templater syntax in my note

  • Confirm your note is saved inside the 00 Inbox folder (drag it there from the file explorer if it landed elsewhere).

Your capture workflow is live. One command creates a note with structured metadata ready for AI tools to parse. Next up, you will build templates for the remaining PARA note types so every note in your vault follows the same schema.

Build the Remaining Core Templates

Your Inbox template is working and you have captured a real note with structured metadata. That proves the pattern works for one note type.

Now you need the same consistent schema on every note that enters your vault. A project note, an area note, a resource note, and a Map of Content all need the same universal YAML frontmatter fields so that AI tools can query them uniformly. In this step, you will create the remaining four templates.

In this step, get ready to:
  • Create Project Note and Area Note templates with type-specific body sections.
  • Create Resource Note and MOC Note templates with additional metadata fields.
  • Test each template by creating a real note and verifying consistent properties across the vault.
Create the Project and Area templates

Project notes track work with a clear outcome. Area notes track ongoing responsibilities with no end date. Both use the same six universal schema fields you built in the Inbox template, but each gets its own body sections.

  • In the file explorer sidebar, right-click the Templates folder and select New note.
  • Name the file Project Note and paste the following content:
<% "---" %>
type: project
status: inbox
created: <% tp.date.now("YYYY-MM-DD") %>
modified: <% tp.date.now("YYYY-MM-DD") %>
summary: <% tp.file.cursor(1) %>
tags: 
<% "---" %>

## Outcome



## Next Actions

- 

## Notes

<% tp.file.cursor(2) %>

What does this template do?

  • The universal schema (type, status, created, modified, summary, tags) is identical to your Inbox template. This consistency is what makes vault-wide AI queries possible.
  • The ## Outcome section forces you to define what "done" looks like for this project upfront.
  • The ## Next Actions section keeps the project actionable instead of abstract.
  • Save the file.
  • Confirm Project Note.md appears in the Templates folder in the file explorer sidebar.

Don't see the file in Templates?

  • Make sure you created the note inside the Templates folder, not at the vault root. Drag it into the folder if needed.
  • Check that the filename is exactly Project Note with no extra spaces or characters.

Why isn't my template showing in the Templates folder?

  • Right-click the Templates folder again and select New note.
  • Name the file Area Note and paste the following content:
<% "---" %>
type: area
status: active
created: <% tp.date.now("YYYY-MM-DD") %>
modified: <% tp.date.now("YYYY-MM-DD") %>
summary: <% tp.file.cursor(1) %>
tags: 
<% "---" %>

## Standards



## Active Projects

- 

## Notes

<% tp.file.cursor(2) %>

How does the Area template differ?

Notice status: active instead of status: inbox. Areas are ongoing responsibilities (health, finances, career) that are always active. They never move through a processing pipeline the way inbox items do.

The ## Standards section captures what "good" looks like for this area. The ## Active Projects section links to projects that serve this area.

  • Save the file.
  • Confirm Area Note.md now appears alongside Project Note.md in the Templates folder.

Template looks wrong in the editor?

  • If you see a pink banner saying "Failed to parse YAML", make sure the first line is exactly <% "---" %> with straight double quotes, not curly quotes.
  • If Obsidian tries to render the frontmatter as Properties, switch to Source mode (Ctrl+E toggles views) and verify the raw Markdown looks correct.

Help me fix YAML parsing errors in my Templater template.

Create the Resource and MOC templates

Resource notes capture knowledge from external sources like articles, books, and videos. They need two extra metadata fields beyond the universal schema: where the knowledge came from and what type of source it is.

  • Right-click the Templates folder and select New note.
  • Name the file Resource Note and paste the following content:
<% "---" %>
type: resource
status: inbox
created: <% tp.date.now("YYYY-MM-DD") %>
modified: <% tp.date.now("YYYY-MM-DD") %>
summary: <% tp.file.cursor(1) %>
tags: 
source: 
source_type: 
<% "---" %>

## Key Ideas

- 

## Quotes / Highlights

> 

## My Thoughts

<% tp.file.cursor(2) %>

What are the extra fields for?

  • source holds the URL, book title, or reference so you can trace the knowledge back to its origin.
  • source_type categorizes the medium (article, book, podcast, video, course, conversation, email). This lets AI tools filter resources by format when answering your queries.
  • The body sections separate raw capture (## Quotes / Highlights) from your own thinking (## My Thoughts). This distinction matters for AI tools that need to know what is yours versus what is cited.
  • Save the file.
  • Confirm Resource Note.md appears in the Templates folder.

Source fields not showing in Properties?

  • The source and source_type fields are blank in the template. They will only appear in Obsidian's Properties panel after you apply the template to a note and fill them in. In the template file itself, just confirm the raw text shows them after the tags: line.

Help me understand why my extra fields don't appear in Properties yet.

The last template is the Map of Content. An MOC is not a traditional note. It is a curated index that links to other notes on a topic, giving you a navigable entry point into a cluster of related ideas.

  • Right-click the Templates folder and select New note.
  • Name the file MOC Note and paste the following content:
<% "---" %>
type: moc
status: active
created: <% tp.date.now("YYYY-MM-DD") %>
modified: <% tp.date.now("YYYY-MM-DD") %>
summary: <% tp.file.cursor(1) %>
tags: 
<% "---" %>

## Overview

<% tp.file.cursor(2) %>

## Key Notes

- 

## Related Maps

-

What makes an MOC different from other notes?

An MOC has status: active because it is a living document that grows as you add notes to its topic. The ## Key Notes section is where you will add links to related notes. The ## Related Maps section connects MOCs to each other, building a navigable hierarchy across your vault.

  • Save the file.
  • Expand the Templates folder in the file explorer sidebar. You should see five files: Inbox Note.md, Project Note.md, Area Note.md, Resource Note.md, and MOC Note.md.

Missing a template file?

  • Click each file to open it and verify the first line is <% "---" %>. If a file is empty, paste the template content from above.
  • If you only see four files, check whether Obsidian created the note at the vault root instead of inside the Templates folder. Drag any misplaced files into Templates.

Help me find a template file that ended up in the wrong folder.

Test each template by creating real notes

Templates only prove themselves when you use them. You will now create one note from each new template in its corresponding PARA folder to confirm the schema populates correctly.

  • Open the command palette (Ctrl+P) and run Templater: Create new note from template.
  • Select Project Note. Name it something real, like Build Second Brain.
  • Move the file into the 01 Projects folder by dragging it in the file explorer sidebar.
  • Fill in the summary field and add at least one tag.

You should see the frontmatter fields populate with today's date and your chosen type. Repeat the process for the other three templates.

  • Run Templater: Create new note from template again and select Area Note. Name it something like Career Development. Move it into 02 Areas.
  • Run Templater: Create new note from template again and select Resource Note. Name it something like PARA Method by Tiago Forte. Move it into 03 Resources. Fill in the source and source_type fields.
  • Run Templater: Create new note from template one more time and select MOC Note. Name it something like Productivity MOC. Move it into 03 Resources.

Now enable the Properties view so you can verify consistency across your vault.

  • Open Settings (Ctrl+,).
  • Click Core plugins in the left sidebar.
  • Find Properties view in the list and toggle it on.
  • Close Settings.

Before you check the results, think about what you expect to see. If all your templates share the same universal schema, what property names should appear in a vault-wide properties list?

  • In the left sidebar, click the All properties tab (it appears after enabling the plugin).

You should see a consistent set of property names: type, status, created, modified, summary, and tags appearing across all notes. If you filled in the Resource note's extra fields, you will also see source and source_type. Every property name is used consistently because every template shares the same schema.

Why does consistency matter for AI?

When every note uses the exact same property names (not date_created in one template and created_at in another), an AI agent can query your vault with a single pattern. It can say "find all notes where status equals inbox" and get reliable results across every note type.

Properties view not showing in the sidebar?

  • Make sure you toggled the Properties view core plugin on (not just the Properties section in Settings). It is a separate core plugin.
  • If you see the File properties tab but not All properties, right-click the sidebar header and select All properties from the available views.
  • If a property name appears with a count of 1 when it should be higher, check that you spelled the property exactly the same in each template (case-sensitive).

Help me get the All Properties view working in my sidebar.

You now have a complete template system. Every note entering your vault, whether it is a quick inbox capture, a tracked project, or a curated resource, carries the same machine-readable schema. Next up, you will fill this vault with real notes across multiple domains.

Populate the Vault With Real Notes

Your vault has five templates that auto-populate structured metadata. You have one test note in each folder proving the system works.

A vault with a few test notes feels tidy, but a real Second Brain needs real content from your actual life. In this step, you will fill your vault with notes from multiple domains and discover firsthand why organization alone is not enough.

In this step, get ready to:
  • Capture 8-10 real notes from work, school, and community domains.
  • Search for a concept that spans multiple folders and observe the flat results.
  • Open Graph View and see every note as an isolated, unconnected dot.
Capture notes from multiple domains

Your vault currently holds a handful of test notes. To experience how a real Second Brain behaves, you need content from across your actual life.

  • Open the command palette with Ctrl+P and run Templater: Create new note from template.
  • Select Inbox Note and create 2-3 inbox captures from what is actually on your mind right now.

Name each note something real. Here are examples to spark ideas:

  • A quick thought you had this morning.
  • Meeting notes from a recent standup or class.
  • A link to an article you want to read later.
  • For each inbox note, fill in the summary field and add at least one tag (e.g., work, school, productivity).
  • Write a few lines of body content in each note so you have something to search for later.
  • Now create 2 project notes using the Project Note template. Make one from work and one from school or a community project.
  • Move each project note into 01 Projects by right-clicking the note in the file explorer and selecting Move file to....
  • Fill in the summary, tags, and the Outcome section for each.
  • Create 1-2 resource notes using the Resource Note template. Think of an article you read recently, a book, or a video.
  • Move them into 03 Resources.
  • Fill in the source and source_type fields in addition to summary and tags.
  • Create 1 area note using the Area Note template for a responsibility you manage (e.g., "Health" or "Finances" or "Team Lead").
  • Move it into 02 Areas and fill in the summary and tags.

You should now have at least 8 notes spread across your PARA folders, each with metadata filled in.

Use tags to mark domains

Consistent domain tags like work, school, and productivity will let you find notes across PARA folders later. A note tagged productivity might live in Projects, Resources, or Areas.

Try to find connections

You now have a vault with real content from multiple domains. Pick a concept that you think appears in more than one note. Maybe it is "productivity", "leadership", a tool name, or a person.

Before you search, think about this: how many notes do you expect to find, and will the results show you how those notes relate to each other?

  • Press Ctrl+Shift+F to open Obsidian's vault-wide search.
  • Type the concept you chose (e.g., productivity or a tool name that appears in multiple notes).

You will find the notes. But look at the results carefully.

The results are flat. There is no indication of how the notes relate to each other, which ones build on which, or what the bigger picture is. Your vault is organized by actionability (which PARA folder it belongs to), not by meaning.

Why can't search show relationships?

Search finds where a word appears. It cannot tell you that your project note depends on a resource note, or that two inbox captures feed into the same area.

The vault is organized like a filing cabinet: things go in the right drawer, but nothing connects the drawers together. That relational structure has to come from somewhere else.

Open Graph View

Obsidian has a built-in graph that visualises how your notes connect. What do you think your graph looks like right now?

  • Press Ctrl+G to open Graph View.

Every note is an isolated dot with no lines between them. The graph tells you nothing because there are no links between notes.

What does the graph prove?

A graph with no connections is a visual confirmation that your PARA system is just a folder structure. It organises, but it does not connect.

Links and Maps of Content are what transform isolated files into a knowledge network that both you and AI tools can traverse.

Graph View showing nothing at all?

If your graph is completely empty, make sure you are in the correct vault. Check the vault name in the bottom-left corner of Obsidian. It should say Second Brain.

If you see dots but they are clustered too tightly, use the scroll wheel to zoom in on the graph.

Help me troubleshoot my Graph View in Obsidian

This is the limitation you will solve in the next step. Your vault has real content, consistent metadata, and clean folder structure. What it lacks is connections between notes that reveal how ideas relate across domains.

Connect Notes With Links and a Map of Content

In the last step, you exposed the core limitation of a PARA vault without links. Your notes are organized by actionability, but the graph shows them as isolated dots with no way to discover connections between domains.

Links transform those isolated files into a knowledge network. In this step, you will weave wikilinks between related notes and build a Map of Content that serves as a navigable entry point for both humans and AI agents.

In this step, get ready to:
  • Add wikilinks between related notes across PARA folders.
  • Build a Map of Content as a curated index for a topic.
  • Verify the connected network in Graph View and Backlinks.
Add links between related notes

A wikilink is Obsidian's way of connecting one note to another. When you type [[ inside any note, Obsidian opens a suggestion menu listing every note in your vault. Selecting one creates a clickable link that both you and future AI tools can follow.

  • Open your first project note in 01 Projects.
  • Find the ## Notes section at the bottom of the note.
  • Type [[ and start typing the name of the area this project belongs to (e.g., your Career Development area note).
  • Select the matching note from the suggestion dropdown and press Enter.
  • Add a second link to a related resource note that supports this project.

Auto-suggest makes this fast

You do not need to type the full note name. Type 2-3 characters and Obsidian narrows the suggestions immediately. This makes linking much faster than you might expect.

  • Now open your area note in 02 Areas.
  • In the ## Active Projects section, add wikilinks to both of your project notes.
  • Open each resource note in 03 Resources and add a wikilink to the project it supports in the ## My Thoughts section.
  • Open each inbox note in 00 Inbox and add at least one wikilink to whatever note it relates to (a project, area, or resource).

Aim for at least 2-3 links per note. The more connections you create, the richer the graph becomes.

  • Open Graph View by pressing Ctrl+G.

You should already see lines forming between your notes. Each wikilink you added creates a visible connection in the graph.

Not seeing any lines?

Make sure you saved each note after adding links. Check that your wikilinks use double brackets [[Note Name]] and that the note name matches an existing file exactly.

If the graph still shows isolated dots, open one of your linked notes and verify the link is clickable (it should appear in a different colour from body text).

Why aren't my wikilinks connecting in Graph View?

Build your first Map of Content

A Map of Content is a special note that acts as a curated index for a topic. Instead of relying on search or folder browsing, you navigate to the MOC and follow links to everything related.

  • Open the MOC note you created earlier in 03 Resources (e.g., "Productivity MOC").
  • In the ## Overview section, write one sentence describing what this map covers.
  • In the ## Key Notes section, add a wikilink to every note related to this topic. Place each link on its own line as a bullet point.
  • After each link, add a short description explaining the relationship (e.g., [[Build Second Brain]] - the active project driving this system).
  • Organize the links by category. Group project links together, area links together, and resource links together.
  • In the ## Related Maps section, leave this empty for now. You will add links here when you create more MOC notes in the future.

What makes a good MOC?

A Map of Content is not an auto-generated index. It is a hand-curated entry point where YOU decide the structure. The one-line descriptions next to each link are what make it valuable. They tell you (and future AI tools) why each note matters in context.

Think of it as the table of contents for a topic that spans multiple PARA folders. It bridges the gap between folder-based organization (actionability) and meaning-based navigation (relationships).

  • Save your MOC note.
  • Click on one of the wikilinks inside the MOC to confirm it opens the linked note.

The link should open the target note instantly. If Obsidian shows a greyed-out link or creates a new empty file, the note name in your wikilink does not match an existing file.

Verify the knowledge graph

Before you open Graph View, think about what you expect to see. Your MOC links to many notes, and those notes link to each other. What shape do you predict the graph will take?

  • Open Graph View by pressing Ctrl+G.

You should see a connected network with your MOC note as a central hub. Lines radiate outward from the MOC to every note it links to. Notes that link to each other also show connections between them.

  • Click on your MOC node in the graph to highlight its connections.
  • Confirm that every link in the MOC resolves to an existing note (no orphan dots labelled with a note name that does not exist).
  • Close Graph View and open your MOC note.
  • Open the right sidebar by clicking the arrow icon on the right edge of the editor.
  • Select the Backlinks tab in the right sidebar.

The Backlinks panel shows every note that links TO your MOC. If you linked any project or area notes back to the MOC, you will see them listed here.

Why do backlinks matter for AI?

Backlinks create bidirectional awareness. When an AI agent reads your MOC, it can follow links forward to find related notes. When it reads any individual note, backlinks tell it which MOCs and parent notes reference it. This two-way traversal is how AI tools understand your vault's structure without needing to parse every file.

Your vault is now a connected knowledge network. You have a navigable, linked system that both you and AI agents can traverse by following wikilinks and Maps of Content. Next up, you will tackle the Secret Mission and build a Daily Note template with conditional automation.

Secret mission

Build a Daily Note Template With Weekly Review

Your templates enforce structure on every new note. But what about the note you create every single day? Build a Daily Note template with a twist: a conditional weekly review checklist that only appears on Fridays, using Templater's JavaScript execution blocks.

Clean Up Your Resources

Clean Up Your Resources

This project runs entirely locally on your machine. There are no cloud resources or ongoing costs to worry about.

Decide whether to keep your vault for daily use or delete it entirely.

Resources you used:

  • "Second Brain" Obsidian vault (local folder containing all notes, templates, and plugin configuration).

Keep everything running

No action needed. Choose this if you plan to use your vault for daily note capture starting today.

  • Your vault is saved locally and ready for daily use.
  • Start capturing notes using your templates immediately.
  • Consider setting up a backup strategy (Git, Syncthing, or cloud folder sync) to protect your vault since everything is stored as local Markdown files.

Pause - I'll come back to this later

Since Obsidian stores everything as local Markdown files, your vault stays on disk whether Obsidian is open or not. No processes to stop, no servers to shut down.

  • Close Obsidian.
  • To pick up later, reopen Obsidian and select the "Second Brain" vault from the vault switcher.

Delete - I don't want to use this again

Remove the vault folder from your machine entirely. This deletes all notes, templates, and plugin configuration.

  • In Obsidian, click the vault icon in the bottom-left corner to open the vault switcher.
  • Note the file path shown under "Second Brain".
  • Close Obsidian.
  • Open a terminal and delete the vault folder by running:
rm -rf [[VAULT_PATH="path to your Second Brain vault folder"]]
  • Confirm the folder is gone by running ls in the parent directory.

Nice Work!

Nice Work!

Nice work! You have built a fully structured Obsidian vault that functions as the foundation for an AI-powered Second Brain.

Every note you create is now automatically stamped with machine-readable metadata, organized by the PARA method, and connected through links.

You've learned how to:

  • Design a YAML frontmatter schema with universal fields (type, status, created, modified, summary, tags) and resource-specific fields (source, source_type) that AI tools can parse programmatically.
  • Create five Templater-powered templates (Inbox, Project, Area, Resource, MOC) that enforce the schema automatically on every new note.
  • Connect notes through wikilinks and build a Map of Content that serves as a navigable entry point for both humans and AI agents.
  • Secret Mission: Built a Daily Note template with conditional weekly review automation using Templater's JavaScript execution blocks.

Ready to quiz yourself?