<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Documentation on NetworkNotes</title><link>https://networknotes.io/docs/</link><description>Recent content in Documentation on NetworkNotes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 02 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://networknotes.io/docs/index.xml" rel="self" type="application/rss+xml"/><item><title>Introduction</title><link>https://networknotes.io/docs/introduction/</link><pubDate>Sun, 31 May 2026 00:00:00 +0000</pubDate><guid>https://networknotes.io/docs/introduction/</guid><description>&lt;p&gt;Most notetaking tools inherit a metaphor from the filing cabinet: a note belongs
in exactly one folder, and folders nest inside folders. It feels tidy. It is also
the reason so many notes are written once and never seen again, buried in a
hierarchy you have to remember in order to retrieve.&lt;/p&gt;
&lt;p&gt;NetworkNotes throws the cabinet out. Here the unit is the &lt;strong&gt;Note&lt;/strong&gt; (a piece of
information you want to keep), the relationships between notes are &lt;strong&gt;Links&lt;/strong&gt; you
create, and the whole
collection forms a &lt;strong&gt;Network&lt;/strong&gt; that grows more useful the more densely it is
connected.&lt;/p&gt;</description></item><item><title>How NetworkNotes Is Different</title><link>https://networknotes.io/docs/how-networknotes-differs/</link><pubDate>Sun, 31 May 2026 00:00:00 +0000</pubDate><guid>https://networknotes.io/docs/how-networknotes-differs/</guid><description>&lt;p&gt;There are plenty of notetaking methods: plain folders, PARA, Building a Second
Brain, Zettelkasten. Strip away the branding and almost all of them answer one of
two questions.&lt;/p&gt;
&lt;h2 id="two-questions-two-families"&gt;Two questions, two families&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&amp;ldquo;Where does this note go?&amp;rdquo;&lt;/strong&gt; is the &lt;em&gt;filing&lt;/em&gt; question: plain folders, &lt;strong&gt;PARA&lt;/strong&gt;,
&lt;strong&gt;Building a Second Brain&lt;/strong&gt;, tag systems. They organise notes by location or
category, and they&amp;rsquo;re good at it. When you know what you&amp;rsquo;re after, you can put
your hands on it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&amp;ldquo;What does this note connect to?&amp;rdquo;&lt;/strong&gt; is the &lt;em&gt;linking&lt;/em&gt; question: &lt;strong&gt;Zettelkasten&lt;/strong&gt;,
evergreen notes, and NetworkNotes. They organise by relationship, so ideas you&amp;rsquo;d
never have filed in the same place can still find each other.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The important part: &lt;strong&gt;these two families aren&amp;rsquo;t enemies.&lt;/strong&gt; Filing tells you where a
note lives; linking tells you what it relates to. You can keep your folders, or
PARA, or whatever grouping you already use, and add links &lt;em&gt;on top&lt;/em&gt;. That&amp;rsquo;s the
first &lt;a href="https://networknotes.io/docs/principles/"&gt;principle&lt;/a&gt;: connect, don&amp;rsquo;t &lt;em&gt;just&lt;/em&gt; file. NetworkNotes never
asks you to dismantle your filing system; it asks you to stop treating filing as the
only structure you get.&lt;/p&gt;</description></item><item><title>Concepts</title><link>https://networknotes.io/docs/core-concepts/</link><pubDate>Sun, 31 May 2026 00:00:00 +0000</pubDate><guid>https://networknotes.io/docs/core-concepts/</guid><description>&lt;p&gt;NetworkNotes is built from a few simple parts. Learn these and the rest of the
system follows naturally.&lt;/p&gt;
&lt;h2 id="the-networknote"&gt;The NetworkNote&lt;/h2&gt;
&lt;p&gt;The whole method is named for it. A &lt;strong&gt;&lt;a href="https://networknotes.io/docs/networknote/"&gt;NetworkNote&lt;/a&gt;&lt;/strong&gt; is a note
connected to at least one other note; it&amp;rsquo;s the thing you are actually building.
Everything else here is either a part of it or a way of working with it.&lt;/p&gt;
&lt;h2 id="the-three-primitives"&gt;The three primitives&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href="https://networknotes.io/docs/note/"&gt;Note&lt;/a&gt;&lt;/strong&gt;: a piece of information you want to retrieve later (any size).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href="https://networknotes.io/docs/link/"&gt;Link&lt;/a&gt;&lt;/strong&gt;: a connection you draw between two Notes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href="https://networknotes.io/docs/network/"&gt;Network&lt;/a&gt;&lt;/strong&gt;: the whole that emerges from many connected Notes.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="seeing-it-the-networkmap"&gt;Seeing it: the NetworkMap&lt;/h2&gt;
&lt;p&gt;A &lt;strong&gt;&lt;a href="https://networknotes.io/docs/networkmap/"&gt;NetworkMap&lt;/a&gt;&lt;/strong&gt; is a visual representation of your Network
(Notes as dots, Links as lines), so its structure (hubs, clusters, orphans) becomes
something you can see at a glance.&lt;/p&gt;</description></item><item><title>NetworkNote</title><link>https://networknotes.io/docs/networknote/</link><pubDate>Sun, 31 May 2026 00:00:00 +0000</pubDate><guid>https://networknotes.io/docs/networknote/</guid><description>&lt;p&gt;A &lt;strong&gt;NetworkNote&lt;/strong&gt; is a &lt;a href="https://networknotes.io/docs/note/"&gt;Note&lt;/a&gt; (a piece of information you want to
remember for later) connected to at least one other Note.&lt;/p&gt;
&lt;p&gt;It is the unit the whole method is named for. A &lt;a href="https://networknotes.io/docs/link/"&gt;Link&lt;/a&gt; is the
connection you draw; a NetworkNote is what a Note &lt;em&gt;becomes&lt;/em&gt; the moment you draw one.&lt;/p&gt;
&lt;h2 id="a-connected-note-not-a-lone-one"&gt;A connected Note, not a lone one&lt;/h2&gt;
&lt;p&gt;On its own, a Note is raw material, a fact in isolation. Give it a
&lt;a href="https://networknotes.io/docs/link/"&gt;Link&lt;/a&gt; to another Note and it stops being isolated: it now has a way in
and a way out, and it can be reached from ideas you haven&amp;rsquo;t had yet. That connected
Note is a NetworkNote. (An unconnected Note is an orphan, a NetworkNote-in-waiting.)&lt;/p&gt;</description></item><item><title>Note</title><link>https://networknotes.io/docs/note/</link><pubDate>Sun, 31 May 2026 00:00:00 +0000</pubDate><guid>https://networknotes.io/docs/note/</guid><description>&lt;p&gt;A &lt;strong&gt;Note&lt;/strong&gt; is a piece of information you want to be able to retrieve later. That is
the whole definition. There are no &lt;em&gt;fixed&lt;/em&gt; types to sort it into (use your own, or
none), and it does not have to be a single tidy idea.&lt;/p&gt;
&lt;h2 id="make-it-whatever-size-is-useful"&gt;Make it whatever size is useful&lt;/h2&gt;
&lt;p&gt;A Note can be atomic: one idea, stated plainly, like &amp;ldquo;spaced repetition improves
retention.&amp;rdquo; It can just as easily hold everything you want to keep about a talk you
gave, a course you took, or a meeting you sat in. You size a Note to the unit you&amp;rsquo;ll
want to pull back later.&lt;/p&gt;</description></item><item><title>Link</title><link>https://networknotes.io/docs/link/</link><pubDate>Sun, 31 May 2026 00:00:00 +0000</pubDate><guid>https://networknotes.io/docs/link/</guid><description>&lt;p&gt;A &lt;strong&gt;Link&lt;/strong&gt; is a relationship you draw between two &lt;a href="https://networknotes.io/docs/note/"&gt;Notes&lt;/a&gt;. You create
one simply by referencing one Note from another. The Link, not the Note, is the
unit of meaning: it says &lt;em&gt;these two ideas belong together&lt;/em&gt;.&lt;/p&gt;
&lt;h2 id="links-are-bidirectional"&gt;Links are bidirectional&lt;/h2&gt;
&lt;p&gt;Every Link you create is visible from both ends. Connect Note A to Note B, and B
gains a backlink to A for free. This is what lets you arrive at an idea from any
direction; the &lt;a href="https://networknotes.io/docs/network/"&gt;Network&lt;/a&gt; has no single front door. The link is still
&lt;em&gt;directed&lt;/em&gt;, though, and that asymmetry carries meaning: see
&lt;a href="https://networknotes.io/docs/directionality/"&gt;Directionality&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Network</title><link>https://networknotes.io/docs/network/</link><pubDate>Sun, 31 May 2026 00:00:00 +0000</pubDate><guid>https://networknotes.io/docs/network/</guid><description>&lt;p&gt;The &lt;strong&gt;Network&lt;/strong&gt; is the whole that many &lt;a href="https://networknotes.io/docs/networknote/"&gt;NetworkNotes&lt;/a&gt; form:
every &lt;a href="https://networknotes.io/docs/note/"&gt;Note&lt;/a&gt; and every &lt;a href="https://networknotes.io/docs/link/"&gt;Link&lt;/a&gt;, taken together. You never
design it. It is an emergent shape, the accumulated residue of many small linking
decisions.&lt;/p&gt;
&lt;h2 id="structure-you-discover-not-decree"&gt;Structure you discover, not decree&lt;/h2&gt;
&lt;p&gt;Over time, clusters form around the ideas you return to most, bridges appear
between fields you didn&amp;rsquo;t expect to connect, and the structure of your own thinking
becomes something you can actually see. A &amp;ldquo;category&amp;rdquo; in NetworkNotes is not a folder
you created; it is a neighbourhood that &lt;em&gt;emerged&lt;/em&gt;.&lt;/p&gt;</description></item><item><title>NetworkMap</title><link>https://networknotes.io/docs/networkmap/</link><pubDate>Sun, 31 May 2026 00:00:00 +0000</pubDate><guid>https://networknotes.io/docs/networkmap/</guid><description>&lt;p&gt;A &lt;strong&gt;NetworkMap&lt;/strong&gt; is a visual representation of a &lt;a href="https://networknotes.io/docs/network/"&gt;Network&lt;/a&gt;: each
&lt;a href="https://networknotes.io/docs/note/"&gt;Note&lt;/a&gt; is a dot, each &lt;a href="https://networknotes.io/docs/link/"&gt;Link&lt;/a&gt; a line between dots.&lt;/p&gt;
&lt;p&gt;It isn&amp;rsquo;t a different thing from your Network; it&amp;rsquo;s the same Network, &lt;em&gt;seen&lt;/em&gt;. But
seeing it changes what you notice.&lt;/p&gt;
&lt;h2 id="what-a-networkmap-shows-you"&gt;What a NetworkMap shows you&lt;/h2&gt;
&lt;p&gt;A list of notes hides structure; a NetworkMap makes it visible at a glance:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Hubs&lt;/strong&gt;: the densely connected dots are your load-bearing ideas.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Clusters&lt;/strong&gt;: tight groups reveal the themes you actually return to.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Orphans&lt;/strong&gt;: dots with no lines are notes still waiting to be connected.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You don&amp;rsquo;t read a NetworkMap so much as &lt;em&gt;navigate&lt;/em&gt; it. It&amp;rsquo;s a map in the literal
sense: for orientation, not prose.&lt;/p&gt;</description></item><item><title>The Three Principles</title><link>https://networknotes.io/docs/principles/</link><pubDate>Sun, 31 May 2026 00:00:00 +0000</pubDate><guid>https://networknotes.io/docs/principles/</guid><description>&lt;p&gt;The primitives describe &lt;em&gt;what&lt;/em&gt; NetworkNotes is made of. Three principles describe
&lt;em&gt;how&lt;/em&gt; to keep it healthy.&lt;/p&gt;
&lt;div class="principle-badge not-prose mt-8 mb-3 flex h-14 w-14 items-center justify-center rounded-2xl bg-sky-500/10 ring-1 ring-sky-500/20" aria-hidden="true"&gt;&lt;svg viewBox="0 0 24 24" fill="none" class="h-10 w-10" stroke-linecap="round" aria-hidden="true"&gt;
 &lt;line x1="6.8" y1="12" x2="17.2" y2="12" class="stroke-sky-500" stroke-width="1"/&gt;
 &lt;circle cx="6.8" cy="12" r="1.7" class="fill-sky-500"/&gt;
 &lt;circle cx="17.2" cy="12" r="1.7" class="fill-sky-500"/&gt;
&lt;/svg&gt;&lt;/div&gt;

&lt;h2 id="connect-dont-just-file"&gt;Connect, don&amp;rsquo;t just file&lt;/h2&gt;
&lt;p&gt;Folders, tags, an &amp;ldquo;events&amp;rdquo; bucket are all fine. They give a note a &lt;em&gt;location&lt;/em&gt;. What
NetworkNotes adds is the &lt;strong&gt;&lt;a href="https://networknotes.io/docs/link/"&gt;Link&lt;/a&gt;&lt;/strong&gt;, which gives a note its
&lt;em&gt;relationships&lt;/em&gt;, the one thing no folder can do, because a note relevant to three
projects can live in only one folder but can link to all three.&lt;/p&gt;</description></item><item><title>Putting It Into Practice</title><link>https://networknotes.io/docs/putting-it-into-practice/</link><pubDate>Sun, 31 May 2026 00:00:00 +0000</pubDate><guid>https://networknotes.io/docs/putting-it-into-practice/</guid><description>&lt;p&gt;NetworkNotes is a &lt;strong&gt;system&lt;/strong&gt;, not a piece of software. There is nothing to
install. It&amp;rsquo;s a way of working with notes (link instead of file, and invest in
connections), and you can practise it in almost any tool that
lets one note point to another.&lt;/p&gt;
&lt;p&gt;That portability is the point. Your notes outlive any app. Pick a tool that fits
how you work today, and take the method with you if you ever switch.&lt;/p&gt;</description></item><item><title>Network Measures</title><link>https://networknotes.io/docs/network-measures/</link><pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate><guid>https://networknotes.io/docs/network-measures/</guid><description>&lt;p&gt;Because your notes form an actual &lt;a href="https://networknotes.io/docs/network/"&gt;Network&lt;/a&gt;, you can &lt;em&gt;measure&lt;/em&gt; it.
That&amp;rsquo;s something a folder of files can never offer. A handful of simple measures,
borrowed from network research, tell you how healthy your network is and where it
needs tending.&lt;/p&gt;
&lt;p&gt;A warning first, because it matters: &lt;strong&gt;these are diagnostics, not scores.&lt;/strong&gt; Glance at
them now and then, act on what they show, and get back to writing. The moment you
start optimising a number, you&amp;rsquo;ve fallen into the exact trap the method is built to
avoid: &lt;a href="https://networknotes.io/docs/principles/"&gt;perfecting the system instead of using it&lt;/a&gt;. They also
mean little when your network is small; a dozen notes is mostly noise. Measures earn
their keep as the network grows.&lt;/p&gt;</description></item><item><title>Centrality</title><link>https://networknotes.io/docs/centrality/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://networknotes.io/docs/centrality/</guid><description>&lt;p&gt;Not all notes pull equal weight. &lt;strong&gt;Centrality&lt;/strong&gt; is the network-research term for how
&lt;em&gt;important&lt;/em&gt; a note is to the structure around it: how much of the network leans on
it. Two kinds are worth knowing for notes; the rest are academic.&lt;/p&gt;
&lt;h2 id="hubs-degree-centrality"&gt;Hubs: degree centrality&lt;/h2&gt;
&lt;p&gt;The simplest centrality is just &lt;strong&gt;degree&lt;/strong&gt;: how many &lt;a href="https://networknotes.io/docs/link/"&gt;Links&lt;/a&gt; a note has
(see &lt;a href="https://networknotes.io/docs/network-measures/"&gt;Network Measures&lt;/a&gt;). Your most-connected notes are your
&lt;strong&gt;hubs&lt;/strong&gt;: anchor ideas that many others connect to or through, the de-facto tables of
contents that emerge on their own. They&amp;rsquo;re where reviewing pays off, because touching
a hub touches everything around it.&lt;/p&gt;</description></item><item><title>Directionality</title><link>https://networknotes.io/docs/directionality/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://networknotes.io/docs/directionality/</guid><description>&lt;p&gt;A &lt;a href="https://networknotes.io/docs/link/"&gt;Link&lt;/a&gt; is not just a connection; it has a &lt;em&gt;direction&lt;/em&gt;. You always
draw it from one note to another, so every link has a &lt;strong&gt;source&lt;/strong&gt; and a &lt;strong&gt;target&lt;/strong&gt;.
Most of the time you can ignore this. When you can&amp;rsquo;t, directionality is the reason.&lt;/p&gt;
&lt;h2 id="a--b-is-not-b--a"&gt;A → B is not B → A&lt;/h2&gt;
&lt;p&gt;&amp;ldquo;Spaced repetition&amp;rdquo; pointing to &amp;ldquo;Memory&amp;rdquo; says one thing: this note draws on, or
leads to, that one. &amp;ldquo;Memory&amp;rdquo; pointing back to &amp;ldquo;Spaced repetition&amp;rdquo; says something
else: this note is supported by, or exemplified by, that one. Same two notes,
opposite arrows, different meaning. The direction is part of what the link says.&lt;/p&gt;</description></item></channel></rss>