Map of Content in Obsidian: 5-Step Setup Guide

Quick Answer: A Map of Content (MOC) in Obsidian is implemented by creating a central hub note that links to related concepts and sub-topics. Start by identifying 5-10 core themes in your vault, create a dedicated index note for each, and actively link relevant notes to these hubs to organically build a scalable knowledge navigation system without relying on rigid folder hierarchies.

As your Obsidian vault grows beyond a few hundred notes, retrieval friction increases. Relying solely on folders creates rigid boundaries, forcing multi-disciplinary ideas into single categories. Relying solely on a flat structure of interconnected links can result in an overwhelming graph where finding a specific starting point feels like navigating a maze without a map.

The Map of Content (MOC) methodology bridges this gap. Popularized within the personal knowledge management (PKM) community, an MOC serves as a curated index or routing hub for your ideas. It allows you to organize knowledge fluidly, creating entry points into clusters of related information.

Implementing this system requires a deliberate shift from filing notes away to actively assembling them. The following guide details the structural and behavioral changes required to successfully deploy MOCs in your daily Obsidian workflow.

Understanding the Role of a Map of Content

A Map of Content operates like an evergreen table of contents for your digital brain. Unlike an automated list generated by search queries or tags, an MOC is manually curated. This manual curation is a feature, not a bug. The act of placing a link onto an MOC forces you to consider how a new piece of information relates to your existing knowledge base.

MOCs exist on a spectrum of maturity. A new MOC might be nothing more than a bulleted list of 10 related notes. A mature MOC might contain structured headings, brief summaries of the linked concepts, and embedded queries. They scale with your understanding of the subject matter, allowing your vault architecture to emerge naturally over time rather than requiring strict upfront categorization.

Step 1: Identify Your Core Themes

Before creating any new notes, evaluate the current state of your vault. The goal is to identify broad areas of interest or active projects that naturally attract the most information.

Do not attempt to map out every possible topic you might ever write about. Instead, look for existing gravity wells—topics where you already have clusters of 15 to 30 notes.

Common examples of core themes include:

• Professional domains (e.g., Software Engineering, Product Management)
• Persistent personal interests (e.g., Fitness, Philosophy, Personal Finance)
• Active, long-term projects (e.g., Book Drafts, Home Renovation)
• Knowledge management infrastructure (e.g., Vault Maintenance, Templates)

Limit your initial selection to 5 to 10 core themes. Creating too many top-level categories early on leads to empty hubs that add maintenance overhead without providing navigational value.

Step 2: Create the Root Home Note

The foundational element of the MOC system is the Home Note, sometimes referred to as the Index or Dashboard. This note serves as the absolute top of your vault’s hierarchy and should be the starting point for navigation.

Create a new note named Home or Index. In Obsidian, you can use a plugin like “Homepage” to automatically open this specific note every time you launch the application.

Your Home note should be structurally minimal. List the 5 to 10 core themes you identified in the previous step and format them as internal links.

An effective Home note structure looks like this:

# Home

## Core Domains
- [[Engineering MOC]]
- [[Leadership MOC]]
- [[Health and Fitness MOC]]

## Active Projects
- [[Website Redesign 2026 MOC]]
- [[Obsidian Workflow MOC]]

Appending “MOC” to the filename of these hub notes is a common convention. It visually distinguishes them from standard atomic notes when viewing the file explorer or the quick switcher, making navigation faster.

Step 3: Build Topic-Specific MOCs

With your Home note routing to your core themes, the next step is populating the individual MOC notes. Open one of your newly created MOC links (for example, Engineering MOC) and begin structuring the space.

A topic-specific MOC should provide a logical flow through the subject matter. Avoid dumping 50 links into a single unordered list. Group the links under logical headings.

Structuring a Domain MOC

If your MOC covers a broad domain, organize the links chronologically, by difficulty, or by sub-topic.

# Engineering MOC

## Architecture Patterns
- [[Microservices vs Monoliths]]
- [[Event-Driven Architecture]]

## Languages & Frameworks
- [[Python Design Patterns]]
- [[React State Management Options]]

## Infrastructure
- [[Docker Best Practices]]
- [[Kubernetes Deployment Strategies]]

Structuring a Project MOC

If the MOC is for an active project, structure it around actionability and reference material.

# Website Redesign 2026 MOC

## Core Requirements
- [[Q3 Design Spec]]
- [[Competitor Analysis 2026]]

## Active Drafts
- [[Homepage Copy Draft 1]]
- [[Pricing Page Tiers]]

## Meeting Notes
- [[Design Sync 2026-04-12]]
- [[Stakeholder Review 2026-04-20]]

Step 4: Develop Linking Habits

The architecture is only useful if it accurately reflects the contents of your vault. Implementing MOCs requires a change in how you process new notes. The standard workflow of “write note and file in folder” must be replaced with “write note and link to MOC.”

There are two primary approaches to establishing these links.

Top-Down Linking

When researching a new sub-topic, start at the relevant MOC. Add a link for the concept you intend to explore before the note even exists. Clicking that placeholder link will create the new note, ensuring it is permanently tethered to the broader domain from its inception.

Bottom-Up Linking

When capturing isolated thoughts or saving highlights from articles, the connection to a broader theme might not be immediately obvious. In these cases, use a bottom-up approach. At the bottom of your new atomic note, add an “Up” link pointing to the most relevant MOC.

# React State Management Options

[Note content here...]

---
Up: [[Engineering MOC]]

This bidirectional relationship ensures that the MOC acts as a parent directory, while the individual note maintains awareness of its context within the larger system.

Step 5: Iterative Refinement and Maintenance

A Map of Content is never finished. It requires ongoing maintenance to remain useful. As you add more notes to a specific MOC, it will eventually become cluttered and difficult to parse.

When an MOC exceeds 40 to 50 links, or when a specific sub-heading within an MOC grows too large, it is time to refactor. Extract that sub-heading into its own dedicated MOC.

For example, if the “Languages & Frameworks” section of your Engineering MOC becomes unwieldy, create a new Languages MOC. Move all the relevant links to this new note, and leave a single link to the Languages MOC on the parent Engineering MOC.

This process of gathering, grouping, and elevating clusters of notes is the core mechanism of emergent knowledge management. It ensures your vault remains performant and navigable regardless of how many thousands of notes it contains.

Practical Advice for MOC Architecture

While the basic implementation of MOCs is straightforward, scaling the system requires specific technical choices within Obsidian.

Balancing Folders and Links

MOCs do not necessitate the complete abandonment of folders. A hybrid approach is often the most practical. Use a minimal folder structure—perhaps just 3 to 5 folders like Attachments, [Daily Notes](/posts/tana-commands-for-automated-daily-note-setup/), Templates, and [Zettelkasten](/posts/zettelkasten-method-explained/) (for all standard notes). Let the MOCs handle the logical organization while the folders handle the file system organization. This reduces the cognitive load of deciding where a file should “live” on your hard drive.

Leveraging the Dataview Plugin

For advanced users, the community plugin Dataview can partially automate MOC maintenance. Dataview allows you to query your vault based on tags, folders, or frontmatter, displaying the results dynamically.

While manual curation forces deeper engagement with the material, Dataview is highly effective for project-based MOCs or logging. For instance, an MOC tracking daily journal entries can use Dataview to automatically list all notes created in the last 30 days tagged with #journal, eliminating the need to manually update the MOC every day.

Utilizing Graph View

Obsidian’s Graph View is enhanced significantly by MOCs. By assigning distinct colors to your MOC notes in the Graph View settings, they become highly visible anchor points. When you filter the graph to show a specific MOC and set the link depth to 1 or 2, you immediately generate a visual cluster of that specific knowledge domain, filtering out the noise of the broader vault.

Frequently Asked Questions

What is the difference between an MOC and an index note?

In practice, the terms are often used interchangeably. However, an index note typically implies a static, alphabetical list of files, whereas an MOC implies a curated, logically structured narrative that groups related concepts together to facilitate thinking and navigation.

How many MOCs should I have in my Obsidian vault?

There is no fixed limit, but you should only have as many as you can actively maintain. Most users start with 1 Home MOC and 5 to 10 top-level domain MOCs. As your vault grows, sub-MOCs will emerge organically. A vault of 5,000 notes might comfortably sustain 50 interconnected MOCs.

Should I use tags or links for my Map of Content?

Links ([[Note Name]]) are significantly more powerful for MOCs than tags (#tag). Links establish direct, bidirectional relationships between specific files, allow for structural formatting, and surface clearly in the graph view. Tags are better suited for status indicators (e.g., #draft, #to-review) or broad, cross-cutting metadata rather than structural organization.

Do MOCs replace folders in Obsidian?

They replace the need for deeply nested, rigid folder hierarchies. Instead of categorizing a note into Engineering/Software/Web/React, you place the note in a single flat directory and use links to connect it to the relevant MOCs. This allows the note to exist in multiple contexts simultaneously without duplicating the file.

How do I know when to create a new MOC?

Create a new MOC when a specific topic or sub-heading within an existing MOC becomes difficult to navigate. A good rule of thumb is the “mental friction test”: if finding a specific note within a cluster takes more than a few seconds of scanning, that cluster has enough mass to warrant its own dedicated Map of Content.