Content distribution
Turn one published article into a native post for every channel you've enabled — X, LinkedIn, Reddit, and Hacker News — each reshaped in that network's own voice and pointing back to the article. Draft-only; you publish manually.
Content distribution is the spoke half of hub-and-spoke: your article is the hub, and each channel post is a spoke that carries the same idea back to where your readers already are. From any article on the Content tab you hit Distribute, and the loop reshapes that one piece into a native draft for each enabled channel — one idea, said natively several ways, never one body cross-posted everywhere. It is draft-only: it never posts. You review each spoke and publish it yourself.
This is distinct from its two neighbours: the Content loop writes the long-form article (the hub) and opens a pull request; the Social content loop drafts original short posts in your own voice. Distribution only ever reshapes an article you already have.
Prerequisites
- An article to distribute. Distribution starts from a content hub — an article written by the Content loop (or generated from the Content tab's Generate article button). Each article registers as a hub and appears as a card on the Content tab; that's what you distribute from.
- Content distribution enabled, with at least one channel picked. Open the settings (the gear on the Content tab), choose any subset of X, LinkedIn, Reddit, and Hacker News, and hit Enable content distribution. The loop drafts for the enabled channels and only those.
- Optionally, a strategy — a
goal, a 1–3 sentencepositioning, and recurringthemes. These are optional and only steer the voice; leave them blank and 1mn reads your product profile,Business.md, andBrand.mdfor context. These are the same channels and strategy the Social content loop uses.
Distribute an article
- Open the Content tab (under Growth in the sidebar). Each article you've generated shows as a card with its cover, title, and links to its PR and published Article.
- On the article you want to amplify, click Distribute. The button reads Packaging… while a sandboxed agent runs (a cold start takes roughly 10–40 seconds), then the drafts appear beneath the card.
- Expand the card's channel drafts row to read each spoke. Every draft shows its channel, format, ready-to-copy body (plus a title for Reddit / Hacker News), and a
Whyline — the one-sentence rationale, including where the article link goes for that network. - Copy a draft, adjust it if you like, and post it manually on that network. To refresh the whole package — for example after enabling another channel — click Regenerate; re-running is safe (see de-duplication).
What each channel gets
The etiquette is the product here — every spoke is written to belong on its network, not to read like the same announcement four times:
| Channel | What the loop writes | Where the link goes |
|---|---|---|
| X | One native long-form post (not a thread) with the strongest line first — it's the feed preview | In the first reply, not the body |
| A native full post: founder-framed, short paragraphs, generous line breaks for a skim-heavy feed | In the first comment, not the post | |
| A genuine value-first post with a title — the lesson first-person, one honest caveat, ending on a question that invites replies | A footnote, not the point; the Why names the best-fit subreddit and flags its self-promo rules | |
| Hacker News | A neutral, mechanism-forward title plus the author's first comment to post immediately — real substance that concedes the strongest counter-argument | Follows HN's own conventions; show up to argue in good faith |
Every spoke carries the article's single core thesis and the same specifics — it never invents a new claim the article doesn't make. If a channel has no strong native angle for a given article, the loop skips it: a weak draft is worse than none.
What you get
Beneath each article, one card per enabled channel that had a strong angle:
A native draft per channel
Channel, format, and the full ready-to-copy body — plus a title for Reddit and Hacker News.
A Why line
The one-sentence rationale, including where the article link belongs on that network.
A link back to the hub
Every spoke stays attached to its source article, so the package reads as one story.
Bodies carry no markdown link syntax — they're plain text you can paste as-is. You publish each one yourself; the loop has no ability to post.
Notes & limits
- Draft-only by design — there is no auto-post setting on any channel.
- De-duplicated per article + channel. Each spoke is keyed to its article and channel, so hitting Regenerate refreshes the existing draft rather than piling on duplicates.
- Quality over coverage. Fewer, stronger spokes beat one weak draft per channel — a channel with no earned angle is left out.
- Grounded in the article. The loop reshapes the piece you wrote; it may pull one current fact to fit a channel, but it won't re-research the whole topic or contradict the article.
- Distribution shares the enabled channels and strategy with the Social content loop — changing channels in one place changes both.
See How loops work for the trust model behind draft-only, and Content for the article loop that produces the hubs you distribute.
Content
One GEO-optimized long-form article per run, scouted, drafted, and committed straight to your website repo's blog directory as a pull request you review and merge.
Social content
A daily draft-only loop that scouts what's happening in your space and writes one channel-native original post per enabled channel — X, LinkedIn, Reddit, or Hacker News — each grounded in a real, current source. It never posts; you review and publish from the Content tab.