Field Notes: Articles That Can Grow Into Guides

I have wanted a place on the internet that I own, where I can write the way I actually learn: in pieces, then in sequences. Not a dump of disconnected posts. Not another “Part 1 of 12” series that dies at Part 3. Something between a blog and a field guide.

That is what Field Notes is for.

The blog I never quite kept

I have always liked the idea of a blog. Write something useful. Publish it. Come back later. Build a body of work.

In practice, blogs lose shape. The first post is clear. The second still stands alone. By the fifth, you are writing for people who already read the other four, or you are repeating yourself so newcomers are not lost. The archive becomes a pile of related thoughts with no good path through them.

Readers feel it too. They land on a post, realize it assumes three others, and bounce. Or they find a “start here” page that is already out of date.

The Part 1/X problem

We have all seen it: a useful series that is really one idea split across URLs.

• Part 1: setup
• Part 2: the thing you actually wanted
• Part 3: edge cases
• Part 4: “I’ll finish this later”

Each post is incomplete on purpose. The order is the product. If you miss a link, or the author never writes Part 5, the knowledge is stranded.

That format works for a course. It is a weak default for a personal site. Knowledge is rarely a straight line. It is notes that cluster, then eventually deserve a spine.

What Field Notes is

Field Notes is an attempt to make that clustering honest and easy.

Posts show up as Articles. An Article is a complete piece. You can read it without homework. It can be a how-to, a note from the field, a decision you would make again, or a mistake you would not.

When several Articles belong together, they become a Guide. A Guide is not a rewrite of everything. It is the path: which Articles to read, in what order, and why they form one subject. The Articles stay themselves. The Guide is the map.

That is the whole model.

• Write when you have something worth saying.
• Group when the pile starts to mean something.
• Keep both visible: the single note and the trail through the notes.

A field guide is useful because it assumes you are in something — a tool, a stack, a practice — and you need orientation, not a novel. Field Notes is that idea applied to a personal publishing site.

Why Articles and Guides instead of “a blog plus tags”

Tags and categories are filing. They do not tell anyone what to read first, what depends on what, or which five posts are actually one topic.

A series of numbered posts forces a sequence even when the ideas are not sequential.

Articles + Guides split two jobs that blogs usually smash together:

1. Capture — get the knowledge out while it is still sharp.
2. Compose — later, turn related captures into something a stranger can follow.

That second step is where most personal sites stall. The writing happened. The curation never did. Field Notes treats curation as a first-class thing, not an afterthought sidebar.

For me, that matters because I will write more if the first post does not have to be the definitive essay. I can publish the fragment. When the fragments accumulate, I can promote them into a Guide without pretending the early posts never existed.

Knowledge I own

There is a second reason for this project, and it is not formatting.

A lot of what people know now lives on platforms they do not control: threads, videos, comments, “I posted this on LinkedIn.” Those places are good at distribution and bad at permanence. The post ages. The algorithm moves on. The context disappears. You explained something well once, and now it belongs to a feed.

I want more of that knowledge on a site I own.

Not because social platforms are useless — they are good discovery layers — but because the source should be mine. If I spend the time to figure something out, I would rather the durable version live in Field Notes, as an Article that can later sit inside a Guide, than as a post that only makes sense in last Tuesday’s timeline.

Owning the knowledge also changes how I write. I am not optimizing for a scroll. I am leaving a trail I can extend.

What I hope this becomes

Field Notes is not a claim that I have invented blogging. It is a small bet on a better default:

• Write Articles that stand on their own.
• When they start to form a subject, make a Guide.
• Keep the work on a site I control.
• Use that structure as an excuse to publish more, not less.

If it works, the site should feel less like an archive of posts and more like a set of notes you can actually use in the field — plus the occasional map that says, “start here, then here, then here.”

That is the project I have wanted to do for a while. This is the shape of it.