From 2,000 Bookmarks to Five Paths: A Curation Story

You don't start with a system. You start with a browser export the file size of a short novel: somewhere north of 2,000 bookmarks, accumulated over roughly four years of "I should read this."

The uncomfortable part isn't the number. It's that you can name maybe ten of them. The rest are a fossil record of past intentions.

The moment of truth

The prompt is mundane: a friend asks how to get into web development. "Send me some good links," they say.

You open your bookmarks to pull together a starter list and spend forty-five minutes failing. You have plenty — three different React intros, a CSS grid cheat sheet saved twice, something called "advanced webpack" from a job you no longer have. What you don't have is an answer to the simplest question a learner asks: where do I start?

Twenty of those 2,000 links, in the right order, would be a better gift than everything you own. You mistook possession for knowledge, and the export proves it.

The audit

You do what anyone does after an unpleasant realization: make a spreadsheet you'll abandon later. But one habit from it sticks — the three-bucket rule for every single link:

1. Promote. If the link answers "would I send this to a friend as the starting point?", it goes into a path.
2. Park. Genuinely interesting, not currently relevant — one single inbox. Not fifteen folders. One.
3. Delete. Everything else. Including the advanced-webpack thing. Especially the advanced-webpack thing.

The numbers after one weekend: ~120 links promoted, ~60 parked, and yes — about 1,800 deleted. You feel nothing for 1,790 of them. That's how you know they were never yours to keep.

The structure that stuck

Promoted links go into paths, and over a few months it settles into exactly five: web fundamentals, React, a Python path for scripting, one for the newsletter's topic, and one embarrassingly useful path about running a household budget. Each is small — a dozen links or so — each has sections in a deliberate order.

The park inbox gets emptied every Friday. Promote or delete, no third option. Fifteen minutes, weekly, no exceptions — that cadence turns out to matter more than any rule above, because it's the week where you're still inside the topic that you know which link deserves the seat.

What actually changed

• Lookups died. "Where's that good Postgres article" became a URL sent in ten seconds.
• Completion went up, weirdly. Not on paths saved for later — on paths built. Building a path means reading the links. Curation turned out to be the studying.
• Sharing made you honest. Every path sent to someone gets a fix before it goes out: a dead link, a missing intro, an ordering that only made sense to the builder.
• The pile shrank and stayed shrunk. Five paths, plus an inbox emptied weekly. The 2,000-link anxiety doesn't come back.

The lessons worth keeping

1. Curation beats collection. The skill isn't finding links; it's refusing most of them.
2. Sequence is the value. The same ten links in a good order teach; in a pile they don't.
3. Teach early. Sending a path to one person fixes more than a month of private tidying.
4. A path is a living document. Two of the five get rewritten entirely over time. That's not failure — that's the point.

Links keep getting saved. The difference is where they land: one inbox, emptied weekly, promoted into paths or deleted. It's less romantic than a second brain. It just works.

If your export tells a similar story, you don't need more discipline — you need somewhere for promoted links to live as sequences. Linkversity is where those live: ordered sections, one shareable URL, weekly inbox included in spirit, if not in software.