You Don't Need a Graph. You Need One Index Note.

The graph view is beautiful and nearly useless for finding anything. The reliable way back to your own notes is one index you wrote by hand: a plain Markdown file whose body is a curated list of links to the topics you actually work on. Not an algorithm's map of your mind. A README for your own thinking.

A previous post argued that the graph view and auto-backlinks are a trap — a topological map of which notes touch, not a record of why. That was the critique. This is the constructive other half. If the machine's picture cannot navigate for you, what does? The answer is older than any app, and it has a name.

What a Map of Content actually is

A Map of Content is a note whose job is to point at other notes. It is a page you author, listing the links that matter, in the order that helps you. Not a folder, not a graph. Nick Milo, who coined the term, defines it plainly: "MOC stands for Maps of Content because these notes map the contents of some of your notes." ¹

The purpose is findability. Milo's own line is "MOCs help you gather, develop, and navigate ideas." ¹ Navigate is the word doing the work. A graph shows you that connections exist; a MOC is the one place you go first when you want to get somewhere. You do not search for it or stumble onto it through an edge. You keep it as your home page and start every session there.

When do you make one? Milo ties it to a feeling, not a count. "Whenever you start to feel that tickle of overwhelm (Mental Squeeze Point), that's when you need to become a cartographer of your own content and create a new MOC." ² The index note is a response to your own confusion. You build it the moment a pile of notes stops being navigable in your head.

The idea is older than the name

The hand-written index predates Obsidian by half a century. Niklas Luhmann's Zettelkasten — "some 90,000 index cards" linked by hand ³ — did not run on a graph view because none existed. It ran on entry points the author placed deliberately. The instinct is not new; the auto-graph is just the part that distracts from it.

Sascha, writing at Zettelkasten.de, describes why Luhmann needed those entry points at all: "So Luhmann created his Zettelkasten to make his note collection surfable. He needed entry points and a mechanism to surf from one note to another in a productive way." ⁴ Surfable is the goal. A box of 90,000 cards with no way in is a box, not a method.

The mechanism he used is exactly the index note under another name. "For example, I have a Structure Note about The Zettelkasten Method. It is similar to a table of contents specifically made of all my Zettel on the topic." ⁵ Structure note, hub note, home note, Map of Content — the labels differ, the move is one thing: a page you wrote that says start here.

Why a hand-written index beats folders

An index note does something a folder cannot: it holds a note in many places at once. A linked note appears on every index where it belongs; a file lives in exactly one folder. Tim Miller, writing at Obsidian Rocks, puts the contrast cleanly. Maps of content "are infinitely flexible. You can add one note to multiple maps, or to none of your maps." ⁶

It is also self-documenting in a way a folder tree never is. Folders demand institutional knowledge: you have to remember the scheme you invented. An index does not. As Miller observes, with folders and tags "you might need a note explaining your file structure," but with maps of content, "the links speak for themselves." ⁶ The index is the explanation. There is no second document describing how the first one is organized.

So the index is not a folder by another name. It is the opposite trade: instead of filing each note into one rigid parent, you write a few pages that gather what belongs together, in plain language, and let one note belong to several. The cost is that you maintain it by hand. That cost is the point.

The graph still has one honest job

The graph view is not worthless. At small scale it does one thing well: it surfaces orphans. A note hanging off the edge with no edges is one no index has caught yet. The glowing constellation is a decent smoke detector for what you forgot to link, even if it is a poor map for where to go now.

That is a narrow, real use, and it is the limit of it. The graph tells you a note is unconnected; it cannot tell you what the note means or where it should live. Past a couple of hundred notes the picture becomes a hairball you admire and never navigate. The orphan-detector job survives at scale only because you act on it by hand, by adding the missing note to an index. The graph flags the gap; you close it.

This is the same conclusion the graph-view critique reached from the other direction. The value was never in the rendered edges. It was in the connection a person decided to make — and writing that decision into an index is how the decision survives.

How to build your home index in an afternoon

You build an index note the way you write anything else: open a plain file and start listing. No plugin, no graph to configure. Your index is just another file you own. Steph Ango, who builds a popular note tool, anchors the approach in one principle: "File over app is a philosophy: if you want to create digital artifacts that last, they must be files you can control, in formats that are easy to retrieve and read." ⁷

Here is a starting template — a plain Markdown home note. Copy it, rename the topics to your own, and link the notes you actually open most weeks:

# Home — start here

> The one page I open first. A curated list, not a complete one.

## Live projects
- [[Project — book draft]]
- [[Project — apartment search]]

## Topics I'm building
- [[MOC — Personal knowledge management]]
- [[MOC — Cooking techniques]]
- [[MOC — Money and taxes]]

## Reference I reach for
- [[Checklist — pre-publish]]
- [[People — contacts and who-knows-what]]

## Inbox to sort
- [[2026-06-15 — loose note]]

Three rules keep it useful instead of becoming a second chore:

• Curate, do not catalog. The index is a short list of what matters, not every note you own. If it tries to list everything, it becomes the hairball you were escaping. Leave notes off on purpose.
• Link by hand, with intent. Add a note to an index the moment you decide it belongs there — that decision is the work, the same human act that makes a manual link better than an auto-backlink. A machine can list; only you can choose.
• Split when it squeezes. When one index gets long enough to feel heavy — Milo's Mental Squeeze Point — break a section off into its own MOC and link to it from home. Indexes nest. That is how the structure grows without collapsing.

The index note travels because it is just a file

The quiet advantage of this method is that the index is not a feature. It is a file. A Map of Content built as a .md document opens in any editor, on any device, for as long as plain text exists. The same property that lets your notes survive a tool you outgrow lets the index travel with your portable Markdown, no export required.

The demand for this pattern is real enough to build tooling around. There is even a dedicated plugin whose author advertises, "My plugin automatically generates a Map of Content for your vault." ⁸ But an auto-generated map lands you back where the graph did: a machine's guess at structure, not yours. The index that finds your notes is the one whose choices you made.

So the tool's only job is to stay out of the way while you write it. A minimal note app that keeps your home index as plain Markdown on your own device is enough, because the map is something you authored, not something that was drawn for you.

Frequently Asked Questions

How do I find my notes again without folders?

Write one index note and keep it as your home page. It is a plain file listing links to your live topics, in your order — "infinitely flexible," in Tim Miller's words, because one note can appear on many indexes. ⁶ You navigate by the map you authored, not by remembering which folder you filed something in.

What is a Map of Content (MOC)?

A Map of Content is a note that points at other notes. Nick Milo, who coined the term, defines it as "Maps of Content because these notes map the contents of some of your notes," and notes that "MOCs help you gather, develop, and navigate ideas." ¹ It is a hand-curated index, not an auto-generated graph.

Do I need a graph view to navigate my notes?

No. The graph is a topological map of which notes touch, not a finder. Its one honest job is spotting orphaned notes you forgot to link. To actually get somewhere, you use an index note you wrote by hand — the connection that helps you navigate is one you chose, not an edge a machine drew.

Should I use folders or a Map of Content to organize my vault?

Use an index. A folder holds a note in one place and needs "a note explaining your file structure"; a Map of Content lets a note live on many maps, and "the links speak for themselves." ⁶ Folders enforce one rigid parent. An index gathers what belongs together and stays self-documenting.

How do I find the right index note to start from?

Keep a single home note as your fixed entry point. Luhmann's Zettelkasten worked because he "needed entry points and a mechanism to surf from one note to another." ⁴ One top-level index — your README — is that entry point. Every other index links back to it, so you never have to hunt for where to begin.

Is an index note just a folder by another name?

No. A folder gives each note exactly one parent; an index lets one note appear on several maps or none. Sascha keeps a "Structure Note... similar to a table of contents," ⁵ readable on its own. The trade is that you maintain it by hand — and that curation is precisely the value a folder cannot give you.

The graph is a portrait of your notes; the index is the door into them. You find your way back not through a picture an algorithm drew, but through a page you wrote that says start here. Maps of Content owe their modern name to Nick Milo's Linking Your Thinking work, ¹ and the deeper habit of the hand-made hub to the Zettelkasten tradition ⁴ — but the file is yours to write. If you want somewhere to keep that home index as plain Markdown on your own device, mnmnote.com stays out of the way while you write it.