Zettelkasten Index: Build Entry Points Into Your Notes

A Zettelkasten index is a note that gives you useful starting points into a collection of linked ideas. Build it around a question, add a few relevant notes, and explain why you would follow each link. You can call a focused entry point a hub note; the useful part is the guidance it gives you.

An index helps you return to research without retracing every reading session. For active work, fenbs can keep the source references and reviewed project context that you want an AI assistant to reuse. Your research collection can stay in the note app where you developed it.

How do you build your first index note?

1. Choose a question you already care about, such as what makes a customer support answer trustworthy. Avoid starting with a category broad enough to contain your entire collection.
2. Find three to seven existing notes that contribute something different: an explanation, a supporting example, an objection, or a practical consequence.
3. Write one sentence beside each link explaining its contribution. Put a useful starting note first, then arrange the others in an order someone could follow.
4. Add a short statement of what you understand so far and one question you still cannot answer. Revisit the index when new reading changes either statement.

Create the index after there is something to connect. An empty map can become a list of topics you feel obliged to fill. Starting with real notes lets the structure reflect your thinking, including connections you did not anticipate when you began reading.

How is an index different from a folder or search?

A folder groups files. Search retrieves matches. An index adds your judgment about where to begin and how ideas relate. The same note can appear in several indexes because a useful argument may contribute to several questions without needing several copies.

Practitioner Sascha Fast describes his own hub notes↗ (opens in a new tab) as a way to work with a topic’s structure and develop ideas. You can use that principle without copying anyone’s complete system. One index that helps with a real question is enough to begin.

What does a small, useful index look like?

Say you are researching support documentation for a small software company. You have notes on uncertainty, examples, and the difference between a troubleshooting instruction and an explanation. A topic label such as “support” retrieves them, but does not tell you how to use them together.

Question: What makes a support answer trustworthy?

Start here: Separate a confirmed result from a plausible explanation.
  Why: Establishes what the answer can safely promise.

Next: Show the expected result after each troubleshooting step.
  Why: Gives the reader a way to check whether the step worked.

Challenge: A detailed answer can still hide an unsupported assumption.
  Why: Tests whether detail is being mistaken for evidence.

Current view: Useful answers make uncertainty and checks visible.
Open question: When does explaining uncertainty overwhelm a beginner?

In your actual note, turn each descriptive title into a link to its supporting note. Keep evidence in those underlying notes, with a reference back to the source. The index gives the route through the argument; it does not need to repeat every quotation, observation, or explanation.

For adjacent writing and capture questions, see the note template, Apple Notes setup, atomic notes, daily notes, and fleeting notes guides.

Which links deserve a place in the index?

Choose a link because it helps someone think, not because it includes the topic name. A good entry can establish a definition, offer evidence, expose a limitation, or connect the question to another field. Give competing interpretations room so the index does not quietly become a collection of agreement.

• Use descriptive link text that tells you what the note argues.
• Explain whether the linked note supports, challenges, illustrates, or extends another idea.
• Keep a source reference beside claims you may need to verify later.
• Leave out notes whose relevance you cannot explain in a sentence.

Your app determines the link mechanics. For example, Obsidian’s internal-link documentation↗ (opens in a new tab) describes note links and custom display text. The transferable habit is to make the reason for following a link clear, whichever app stores the notes.

When should you split or revise an index?

Revise an index when its route stops matching your understanding. A strong objection may belong near the beginning rather than under a final miscellaneous heading. A dead end may be worth retaining with an explanation, so your future self does not repeat the same investigation.

Split an index when it has two distinct questions with different starting points. For example, trustworthy support answers and organizing a support team can share some notes while needing separate routes. Keep a short link between the indexes explaining their overlap instead of moving every note into exclusive categories.

For research that informs a product update, a release notes template handles the separate job of explaining the resulting change. The index should preserve the reasoning you may revisit, while the release note communicates what users can now do.

What should an AI assistant receive from the index?

Give an assistant the question, the relevant source links, and a reviewed explanation of what the notes establish. Identify disagreement and missing evidence. A link alone does not tell an assistant whether you endorse an argument, reject it, or merely intend to investigate it.

Keep a research insight separate from a project instruction. Your notes may suggest that shorter troubleshooting answers work better in one setting; that does not make “always shorten support answers” an approved rule. fenbs keeps project context and Decisions and rules separate so people can record what actually applies to the work.

How to do this with fenbs

1. Create a free account and add the project your research is helping.
2. Save the important index or source references in Links and listings. Give each a description that explains its relevance to the project.
3. Add reviewed context notes stating the useful findings, their limits, and where to check the evidence. Record a person’s approved choice in Decisions and rules.
4. Use the integration guide for your supported AI app to connect it. Ask it to read the project context before working and save progress before the session ends.

fenbs does not provide a visual note graph or automatically import your research collection. Keep using your note app if your whole task is personal reading and linking. Add fenbs when those notes need to guide ongoing work across assistant sessions; the second-brain guides cover the broader choices.