Split your notes: shelf vs. story

2026-05-25 · information design · learning workflow

You will collect two kinds of knowledge while learning the web. The first kind is lookup: a URL, a default value, a one-line fix. The second kind is memory: why the fix worked, what you tried first, what made you distrust your own CSS. If both kinds live in one document, the document becomes useless for either job—too long to scan, too thin to teach.

This site splits them on purpose. Resources is the shelf; Journal is the story. The split is not bureaucracy—it is how you keep a public site honest when your private bookmarks are already messy.

The shelf: built for speed

Shelf entries should pass three tests before they ship:

• Task-named — the description says when to open the link, not how much you like the site
• One screen — you can scan a section during a bug without scrolling through diary prose
• Stable URL — the href points at the canonical doc or tool; commentary lives beside it, not instead of it

Example of a useful shelf line: “Open MDN when two tutorials disagree about default display.” Example of noise: “MDN is amazing, changed my life.” The second line feels good and helps nobody at 11 p.m.

The story: built for recall

Journal pieces answer questions the shelf cannot:

• What problem were you solving when the layout broke?
• Which change actually fixed it—and which changes were red herrings?
• What would you do differently if the page used a framework later?

A good story has headings you can search months later (“bisect the DOM”, “test at 780px”). It does not need daily updates; it needs a clear takeaway you would trust if a friend sent you the link.

Cross-link without cloning

Splitting only works if the two layers talk to each other lightly:

• From a journal essay, link to a section on Resources (“see Specs and reference reading”) instead of pasting the same URLs again
• From a shelf entry, link to a journal essay when the “why” is longer than two sentences—especially for habits and debugging
• On Home, show summaries of recent stories; keep the full archive on the Journal index

Duplicated URLs are not just maintenance debt—they train readers to ignore one of the copies. Pick a canonical home for each link; everywhere else, point at that home.

A maintenance rhythm that scales

Try this cadence for a month:

• Day you find a link — add it to the shelf with a when-to-use line; stop there
• Third time you explain the same “why” — promote the topic to a journal essay with steps and a takeaway box
• Six months without opening a shelf link — move it to private bookmarks or delete it; public pages should feel curated, not archaeological

You are not running a museum of every tab you ever opened. You are running a desk someone else could sit at and start working.