Documentation
Concepts
Maps of Content

Maps of Content

Imagine your personal knowledge base as a vast library. Without a catalog system, finding specific information becomes increasingly difficult as your collection grows. Maps of Content (MOCs) serve as that catalog system—they provide structure, context, and pathways through your interconnected notes.

Understanding Knowledge Structure

Every document naturally forms a hierarchy. Take this simple example:

# Projects

## Web Development

Building responsive websites

## Data Science

Analyzing customer behavior patterns

Here, “Web Development” and “Data Science” are children of “Projects,” while the descriptions belong to their respective headers. This creates a tree structure that provides context.

The Power of Contextual Search

This hierarchical structure enables smarter search results. Instead of just finding isolated matches, you get contextual breadcrumbs that show exactly where information lives:

Searching for “web”:

Projects > Web Development

Searching for “proj”:

Projects > Web Development
Projects > Data Science
Projects

The context helps you understand not just what you found, but where it fits in your broader knowledge system.

Scaling with Maps of Content

Individual document hierarchies work well for single files, but what about organizing thousands of interconnected notes? This is where Maps of Content shine.

An MOC is simply a note that contains links to other related notes, creating navigational pathways through your knowledge:

# Projects MOC

## Active Projects

[[Website Redesign]]

[[Customer Analytics Dashboard]]

[[Personal Blog]]

## On Hold

[[Mobile App Prototype]]

[[E-commerce Integration]]

## Completed

[[Marketing Site]]

[[User Authentication System]]

Building Knowledge Hierarchies

MOCs can reference other MOCs, creating multi-level organizational systems:

# Personal Knowledge System

[[Work Projects]]

[[Learning Notes]]

[[Personal Interests]]

This creates search results with deep context:

Personal Knowledge System > Work Projects > Website Redesign
Personal Knowledge System > Learning Notes > JavaScript Frameworks
Personal Knowledge System > Personal Interests > Photography Techniques

Structure Notes: Beyond Simple Lists

While basic MOCs organize through lists, Structure Notes explicitly document relationships between ideas, creating more sophisticated knowledge architectures.

Hub Notes as Knowledge Gateways

Not every note needs direct inclusion in your main MOCs. Instead, create specialized hub notes that serve as entry points to specific domains:

# Software Development MOC

[[Frontend Development Hub]]

[[Backend Systems Hub]]

[[DevOps Hub]]

[[Learning Resources Hub]]

Each hub note then contains detailed connections within its domain, preventing your main MOCs from becoming unwieldy.

Two Types of Links: Structure vs. Content

Understanding the distinction between structural and conceptual connections is crucial for effective knowledge organization:

Structure Links: Administrative Organization

These links organize knowledge for navigation and discovery:

  • Categorizing notes by topic area
  • Creating workflow sequences
  • Building hierarchical indexes
# Psychology MOC

[[Cognitive Psychology]]

[[Social Psychology]]

[[Developmental Psychology]]

These links don’t imply that cognitive psychology directly relates to social psychology—they’re organizational tools.

Content Links: Intellectual Connections

These links represent genuine conceptual relationships:

  • Ideas that build upon each other
  • Evidence supporting arguments
  • Examples illustrating principles
# Habit Formation

The [[Habit Loop]] consists of cue, routine, and reward. This process
is driven by [[Dopamine Pathways]] in the brain, which explains why
[[Variable Reward Schedules]] are so effective at maintaining behavior.

Here, the links connect related concepts based on their intellectual relationships.

Practical Benefits of This Distinction

Clearer Organization: Structure links in MOCs create navigation without forcing artificial conceptual connections. The same note can appear in multiple MOCs based on different organizational needs.

Flexible Reuse: A single atomic note can serve multiple structural contexts while maintaining its distinct conceptual connections.

Better Discovery: Understanding which type of link you’re following helps you know whether you’re navigating organizationally or following a chain of reasoning.

Best Practices for Effective MOCs

Start Simple

Begin with broad categories and refine over time:

# My Knowledge System

[[Work]]

[[Learning]]

[[Personal]]

Create Clear Entry Points

Ensure important Structure Notes are easily discoverable through main MOCs. Your most valuable knowledge should never be more than 2-3 clicks away.

Maintain Regularly

As you create new notes, update relevant MOCs and Structure Notes. Set aside time weekly to review and refine your organizational structure.

Use Descriptive Titles

Instead of generic names like “Misc Notes,” use specific, searchable titles that clearly indicate content and purpose.

Balance Breadth and Depth

Create enough structure to aid navigation without over-organizing. Some chaos in knowledge systems can lead to serendipitous discoveries.

Building Your MOC System

Maps of Content transform scattered notes into navigable knowledge landscapes. They provide the structural backbone that makes large personal knowledge bases not just manageable, but genuinely useful for thinking and creating.

Start with a few broad MOCs covering your main areas of interest. As your system grows, develop specialized Structure Notes to handle complex relationships between ideas. Remember that your MOC system should evolve with your thinking—it’s a living organizational structure, not a rigid filing system.

The goal isn’t perfect organization, but rather creating pathways that help you rediscover your own insights and see connections you might otherwise miss.

Learn More

Unique Features