📝 Lesson 3.3: Maps of Content & Structure Notes

The "Pile of Notes" Problem

Here's a milestone almost every Obsidian user hits, usually somewhere between 50 and 200 notes. The early days felt great: you wrote notes, you linked them, the graph grew. Then one day you open your vault and feel a small dread — "I have a lot of notes now… and I don't know where anything is." New notes go in, but you rarely find your way back to old ones. Your knowledge has quietly become a pile.

The instinct is to reach for folders. Surely if you just organize everything into a clean folder tree, order will return? It won't — at least not the kind of order you actually need. We saw why in Lesson 3.1, but it bites hardest exactly here, so let's name the three reasons folders fail at scale:

• One note, one folder. A note about "deliberate practice" belongs to Learning, Music, and Career at once — but a folder forces you to pick one and bury it from the others.
• Folders don't show relationships. A folder is a container, not a connection. Putting ten notes in a folder tells you nothing about how they relate, which matters more, or where to start reading.
• Deep trees hide things. The tidier and more nested your folders get, the more clicks it takes to reach any note — and the more notes vanish into branches you never open.

So the real problem isn't "my folders aren't neat enough." It's that a growing vault needs entry points — curated places to start — and folders don't provide them. That's the gap a Map of Content fills.

What a Map of Content Actually Is

A Map of Content (MOC) is refreshingly simple:

A Map of Content is just a note whose job is to link to other notes on a topic. It's a hand-curated hub — a table of contents you write yourself — that gathers the scattered notes about one subject into a single starting place.

That's genuinely all it is. There's no special "MOC" button, no plugin required, no magic syntax. A MOC is an ordinary Markdown note; what makes it a MOC is its purpose: instead of holding content, it holds links to content, arranged and annotated by you. The term comes from Nick Milo, who popularized MOCs as a way to bring "just enough" structure to a linked vault without caging it in folders.

A small MOC for a topic might look like this:

# 🗺️ Personal Finance MOC

The hub for everything I'm learning about money.

## Foundations
- [[Compound Interest]] — why time matters more than amount
- [[Emergency Fund]]
- [[Budgeting Basics]]

## Investing
- [[Index Funds]]
- [[Risk & Reward]]
- [[Dollar-Cost Averaging]]

## Books & Notes
- [[Book - The Psychology of Money]]
- [[Book - I Will Teach You to Be Rich]]

## Open questions
- [[How much should my emergency fund be?]]   (still a ghost — to write)

Notice a few things about that note. It's organized with headings, so the topic has shape. Each link has a little context ("why time matters more than amount"), so you're not staring at bare titles. It even includes a ghost link to a note you haven't written yet — the MOC doubles as a to-do list of what's missing. This is a curated, human view of a topic, and no folder or search result can match it, because you decided what belongs, what to call the sections, and how to describe each piece.

MOCs vs. Tags vs. Folders

You now have three ways to bring order to a topic: put notes in a folder, give them a tag, or gather them in a MOC. They're not rivals — they're different tools — but knowing what each is best at keeps you from misusing them.

The key distinction is curation. A tag like #finance auto-collects every note you tagged — including half-baked ones, in no meaningful order. A MOC contains only the notes you chose to feature, in the order and grouping you think makes sense, with your notes about why each matters. A tag answers "what's tagged finance?"; a MOC answers "if I wanted to actually learn or navigate finance, where should I start and what path should I take?" That human judgment is the whole point.

Hub-and-Spoke & the Home Note

MOCs naturally arrange themselves into a hub-and-spoke shape: the MOC is the hub, and each note it links to is a spoke. Zoom out and a healthy vault looks like a set of these little wheels — and above them all sits one master hub: your Home note.

A Home note points to a handful of topic MOCs (hubs); each MOC points to its individual notes (spokes). Two or three levels are plenty.

🏠 The Home note: your vault's front door

A Home note (also called a home page or dashboard) is a single note you open first every time — the lobby of your vault. Its job is to answer "where do I go from here?" in one glance. A good Home note usually gathers:

• Links to your top MOCs — the handful of big topics you care about most
• Quick links — today's daily note, your inbox/"to process" note, your learning journal
• Maybe a "currently working on" section — active projects front and center

# 🏠 Home

## 🗺️ Maps of Content
- [[Personal Finance MOC]]
- [[Health MOC]]
- [[Work MOC]]
- [[Learning MOC]]

## ⚡ Quick links
- [[Inbox]] — stuff to sort later
- [[Learning Journal]]
- Today's note: create/open your daily note

## 🚧 Currently working on
- [[Project - Course Launch]]
- [[Project - Kitchen Remodel]]

Why hub-and-spoke beats a deep tree

A folder tree can be ten levels deep and still leave you lost. A hub-and-spoke vault stays shallow and navigable: from Home, you're two clicks from almost anything — Home → MOC → note. And because spokes are links, a single note can be a spoke on several hubs at once (Compound Interest can live on both the Finance MOC and a Learning MOC). You get structure and the many-contexts freedom of links. That's the best of both worlds, and it's why this pattern has become the default way serious Obsidian users organize.

"Notes Want to Be Found": When to Build a MOC

Here's the single most important habit in this whole lesson, and the one beginners get backwards.

Do not build your MOCs upfront. The tempting move — on day one, sit down and design a gorgeous set of empty MOCs for every topic you might write about — is a trap. You'll spend an afternoon building elaborate hubs for topics you have two notes on, the structure won't match how your thinking actually develops, and you'll have done a lot of "organizing" without learning anything. It's folder-tree perfectionism wearing a new hat.

Instead, follow the principle that Nick Milo phrases as "notes want to be found." The idea: let structure emerge from your notes rather than imposing it in advance. You keep writing and linking. A topic naturally accumulates notes. At some point you notice a cluster — five, eight, a dozen notes that clearly belong together and that you keep wishing you had a single place to see. That is the signal. That's when the cluster is "asking" for a hub. So you make one, right then, from real notes that already exist.

Two tools you already know make emergence easy to spot:

• The graph (Lesson 3.2) shows clusters visually — a dense knot of notes is a MOC waiting to happen, and the hub it forms around might already be a natural home.
• Backlinks (Lesson 3.1) tell you when a note is becoming a hub on its own — if fifteen notes link to your "Sleep" note, "Sleep" is quietly turning into a MOC whether you planned it or not. Lean into it: add some headings and organize those backlinks into a real map.

A Peek Ahead: Letting Dataview Help

Everything so far has been hand-curated — and that's a feature, because human judgment is what makes a MOC valuable. But there's a natural question: "do I really have to update these link lists by hand forever?" Not entirely.

Later in the course you'll meet a community plugin called Dataview, which can query your notes and generate lists automatically. Inside a MOC, a Dataview block can say, in effect, "list every note tagged #finance, sorted by date" and keep that list current on its own:

## All finance notes (auto-generated)
```dataview
LIST
FROM #finance
SORT file.name ASC
```

That's a dashboard note in miniature — a MOC where part of the content is live and self-updating. The sweet spot most people land on is a hybrid: hand-curate the important part (the "start here," the recommended path, the annotations) and let Dataview handle the exhaustive "everything tagged X" part underneath. Best of both — human meaning on top, machine completeness below.

⚠️ Important Note: Don't rush to Dataview now. Its power is wasted if you don't first understand why MOCs matter and how to curate one by hand. Master the manual version this lesson; automate the tedious parts later, once the plugin will genuinely save you time. Foundations first — the same rule from Lesson 1.1.

🎯 Project: Your Home Note & First MOC

Two notes, real structure. You'll build the front door to your vault and the first proper hub for your biggest cluster — using the notes you already have from earlier lessons.

# 🗺️ Health MOC

My hub for everything I'm learning about feeling good day to day.

## Foundations
- [[Sleep]] — the master lever
- [[Caffeine]] — helps focus, hurts sleep after 2pm
- [[Exercise]]

## Habits & routines
- [[Morning Routine]]
- [[Focus]]

## To write
- [[Sleep Hygiene]]   (ghost — my next note)

---
🏠 Back to [[Home]]

Best Practices for MOCs & Structure Notes

✅ Do's

• Let MOCs emerge. Build one when a cluster asks for it, from notes that already exist.
• Add context to each link. A phrase per link turns a bare list into a real map.
• Give the MOC headings. Structure inside the hub is what beats a flat tag list.
• Keep one Home note as your front door and link it to your MOCs both ways.
• Use ghost links in MOCs to mark notes you still want to write.

❌ Don'ts

• Don't pre-build empty MOCs for topics you barely have notes on.
• Don't try to include every note — a MOC is curated, not exhaustive.
• Don't nest MOCs endlessly. Two or three levels (Home → MOC → note) is plenty.
• Don't reach for Dataview yet. Master hand-curation first; automate later.

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

You've solved the problem that quietly defeats most note-takers: the growing pile. Your vault now has a front door and at least one real hub, and — more importantly — you have a principle for adding structure that scales gracefully: let it emerge, curate by hand, keep it shallow. This is exactly how long-time Obsidian users keep vaults of thousands of notes navigable. You're doing it the right way from the start.

❓ Common Questions at This Stage

🔭 Looking Ahead

You've now finished Module 3 — the linking superpower, the graph, and structure notes. Next we widen the lens to methods: proven note-taking systems like Zettelkasten, PARA, and atomic notes. You'll see how MOCs, links, and tags fit into bigger frameworks — and how to borrow the best of each without becoming a slave to any.

✅ Before the Next Lesson

• Finish your Home note and first MOC — you'll build on them next module
• Bookmark or pin Home and actually open it first for a few days
• Notice one more cluster forming; jot its future MOC name in your journal
• Write your Learning Journal entry for this lesson

📚 Additional Resources

• Obsidian Help — Internal links (the basis of every MOC)
• Obsidian Help — Bookmarks (pin your Home note)
• Nick Milo — MOCs Overview (Linking Your Thinking)