From a Raw Idea to a Published Post: The Full InterlinedList Workflow

Sun May 17

Foundational series, post 4 of 5.

This isn't a feature list.

It's a single session — from an idea I had this morning to the entry you're reading now, walked through step by step with the actual decisions I made along the way.

The Starting Point: A Raw Capture

This morning I had a thought while reading something else: most productivity tools are designed for a single role — either for capturing or for writing or for publishing. Nothing is built for the handoff between them.

Three lines. Not a post. The seed of one.

I opened InterlinedList, pressed New Entry, wrote three sentences. Tagged it tools, workflow, productivity. Linked it to two earlier entries I'd already written — one about why I stopped using Notion for drafts, one about the friction between writing environments and publishing platforms.

That's a raw capture. Two minutes. The entry is now in Draft, tagged, linked, and part of the corpus. If I never come back to it, it's still searchable and findable. If I come back in six months, the links still work and the context is still there.

Moving Into Research

A few hours later I had more to say. I came back to the entry and opened the Research panel.

I added three things:

A link to a piece I'd read last week about the history of outlining software, with a note about the relevant section
A quote I'd saved earlier from an essay about writing workflow: "the tool that captures the idea is almost never the tool that publishes it"
A reference to another entry in my corpus — a post I wrote about the first time I used an interlined model for a technical series

None of this is in what you're reading now. It was context I kept visible while drafting. It lives in the research list, not in the published entry.

Drafting: Writing Toward Structure

I started drafting. Not from a blank page — from the three-line capture, with the research panel open and the linked entries visible in the context panel.

Writing with the interlined model means writing in relation to what already exists. I'm not trying to explain everything in one entry. I'm writing this entry's portion of the argument, knowing the entries it links to cover adjacent ground and that future entries in this series will extend what I'm writing now.

That changes how you draft. Less pressured. You don't have to be exhaustive — you have to be specific. This entry does this work. The rest of the series does the rest.

I turned the three-line capture into a few hundred words. Moved through a rough outline: raw capture, research phase, drafting, stage management, publishing. Used AI assistance once — I selected a paragraph that was trying to say too much and asked it to tighten relative to the linked entries it was adjacent to. It identified two sentences that were repeating something an earlier linked entry already said and suggested cuts. I accepted them.

Drafting took about an hour. The entry had been saving automatically the whole time.

Stage Management: Draft to Staged

When I finished the main draft, I didn't publish it immediately. I moved it to Staged.

Staged is the step where I've decided the entry is complete — I'm not going to keep revising it — but I'm not yet ready to make it live. Maybe I want to let it sit for a day. Maybe I'm batching entries to publish on a schedule. Maybe I want a final read on a different device.

In this case, I moved it to Staged because this entry is part of a series, and I want the earlier entries live before this one. The series progress view on the Dashboard shows me: entries 1, 2, and 3 are live. This is entry 4. Entry 5 is drafted. The sequence is right.

Publishing and Syndication

This morning I moved the entry from Staged to Live.

The publish dialog appeared. Because I have Mastodon and Bluesky connected, it showed me the adapted previews for each:

Mastodon: the first two paragraphs formatted as a thread opener, with the full entry title and a link to the InterlinedList post
Bluesky: a condensed summary card with the entry title, the opening line, and a link

I checked both previews, made a small edit to the Bluesky card — the auto-generated summary used a phrase I wouldn't have chosen — and pressed Publish.

The entry went live on InterlinedList. The Mastodon thread went out. The Bluesky card went out.

The entry's sync state on the Dashboard now shows In sync — the source matches what was published. If I edit the source later, the Dashboard flags it as Drifted and prompts me to decide whether to update the published version.

The Full Arc, Compressed

8:40 AM — Raw capture: three lines, two tags, two links. Two minutes.
11:15 AM — Research panel: three items added. Fifteen minutes.
11:30 AM to 12:30 PM — Drafting: full entry written, AI tightening on one section. One hour.
12:30 PM — Moved to Staged. Fifteen seconds.
Next day, 8:00 AM — Moved to Live, syndicated to Mastodon and Bluesky. Three minutes including the Bluesky edit.

Total time from raw idea to published entry: roughly ninety minutes of active work across two sessions.

What Made It Work

The interlined model contributed to every phase.

At capture: tags and links were in place from the first two minutes. No retroactive organizing required.

At research: the research panel kept source material visible alongside the draft without cluttering the published output. No context-switching between apps.

At drafting: the linked entries in the context panel made clear what ground was already covered, so the draft could be specific rather than exhaustive.

At AI assistance: the tightening suggestion was informed by the linked entries, not just the selected text. It caught a redundancy I would have missed on a manual read.

At staging: the series progress view showed where this entry fit in the arc before I published it.

At publishing: the syndication dialog handled platform-specific formatting. I made one edit to one card. Everything else was ready.

None of these steps were complicated. They were just present — available in the flow without requiring a separate tool or a manual context-switch.

That's the workflow.

Next post in the series covers syndication in more depth — specifically how the platform-specific adaptation actually works across Mastodon, Bluesky, and LinkedIn.

— Adron