Zettelkasten in Goodnotes: Connect Handwritten Ideas

You can build a Zettelkasten in Goodnotes by giving each idea its own page, adding typed links between related pages, and maintaining an index of useful starting points. Keep handwriting for thinking and diagrams; use typed labels for dependable navigation.

The goal is a collection you can use again when researching or writing, rather than a stack of attractive reading notes. fenbs can keep the reviewed project conclusions and next steps you select from that collection available to connected AI assistants.

How do you set up your first notebook?

1. Choose one question you are already investigating, such as what helps a reader understand a complex diagram. Start with material that has a real use.
2. Create a notebook for permanent ideas. Reserve an opening page for an index and use a separate notebook for rough reading notes.
3. Put one claim on each permanent page. Add a typed title and a short reference label, such as D014, alongside your handwritten explanation.
4. Record the source title, author, and exact page or section. Distinguish words copied from the source from your interpretation.
5. Connect the new page to one relevant existing idea, then add an index entry only if the page is a useful route into the subject.

Do this with three ideas before organizing your whole library. A single notebook keeps the first experiment easy to inspect. Your reference labels do not need to encode a topic or reproduce an elaborate numbering system; they simply give you something recognizable to write beside a link.

The second-brain guides cover the broader practice of keeping reusable knowledge. Here, the practical test is narrower: can one handwritten idea lead you to another idea that changes how you understand it?

How do you add links between handwritten pages?

Goodnotes creates links on typed text, not directly on handwriting. Its linking instructions↗ (opens in a new tab) support destinations on pages in the same or another notebook or whiteboard. Internal links are not supported in Text Documents or Study Sets, and a destination is a page rather than a precise handwritten passage.

1. Add a small typed label beside the handwritten connection, such as Compare with D009: familiarity can hide confusion.
2. Select the typed words, open Link, and choose Link Settings. Set the destination to Document, then choose the notebook and target page.
3. Confirm by selecting outside the popover on Apple devices, or selecting the checkmark on Android, Windows, or Web.
4. Follow the link and check the destination. Add a separate return link on the other page when the connection is useful in both directions.

Write why the connection matters before linking it. For example, a page arguing that diagrams reduce reading effort might point to a page explaining when unfamiliar symbols increase that effort. The link now records a qualification you can use, rather than merely saying both pages concern diagrams.

What should a handwritten idea page contain?

Give the page enough context to make sense outside the reading session. A title such as Clear labels reduce interpretation work tells you more than Chapter four. Follow it with your explanation, one example, the source reference, and a question or limitation.

A page can include several sentences or a sketch. Keep one main claim so you can refer to it without bringing unrelated arguments along. If the page needs two separate conclusions, give them separate homes and connect them.

For project use, an AI second brain needs selected meaning as well as saved material. Transfer a checked explanation into fenbs context notes when an assistant needs it; the handwritten page can remain the place where you developed the thought.

How do you find an idea again?

Use your index to answer working questions: How should we label diagrams? is a better entry than Miscellaneous design. Under each question, add a few typed links with short explanations. An index should suggest a route through the collection, not list every page.

Goodnotes search↗ (opens in a new tab) can find handwriting, typed text, and other indexed content across the library or within an open document. Imported PDF text needs an existing searchable text layer; Goodnotes does not add that layer to imported PDFs. Search for both the concept and the typed reference label when testing your setup.

Keep names consistent enough to recognize, but include natural synonyms in your own explanation. A reader may remember legend where you wrote key. Try retrieving an older page without looking at your recent notes; that exercise reveals missing vocabulary more quickly than adding more folders.

What usually makes this setup hard to maintain?

The largest problem is treating every highlight as a permanent idea. Capture freely during reading, then promote only the passages you can explain and connect. A copied page does not become useful just because it has a reference label.

• Overloaded pages: separate claims when a link would otherwise land beside several unrelated thoughts.
• Unexplained links: add whether the destination supports, challenges, extends, or illustrates the claim.
• Fragile navigation: check links after reorganizing pages and keep typed titles as a second route.
• Endless maintenance: review the notes needed for current work instead of repairing the whole collection first.

Keep a small manual list of incoming connections if you need to know which pages depend on an idea. Do not build your routine around assumed automatic backlinks. This workflow relies on links and relationships you deliberately create and review.

How to do this with fenbs

1. Create a free account and add the project your research supports. One person can start free, with no credit card.
2. Manually add the reviewed conclusion to context notes, including the notebook name, typed page title, reference label, and an accessible source URL when available.
3. Record a person’s actual project choice in Decisions and rules. Keep an interesting hypothesis labeled as uncertain until someone verifies it.
4. Add a task for the next check, then ask a connected assistant to read the context before working and save Where we left off before stopping.

The fenbs workflow keeps those conclusions and actions with the project. fenbs does not import Goodnotes or read handwritten pages, so a private notebook reference needs a useful written explanation beside it.

fenbs is not the right fit if you only want a handwritten notebook and personal page links. Add it when the selected research needs to become continuing work across AI sessions; portable AI memory explains that distinction.