Goal: start using Postline on its own tooling — a real campaign per tool/library, planned and queued, rather than ad-hoc posting.
This is both the content work and the best dogfooding test for the AI campaign planner.
Candidates
The libraries that already have something to show: bun-query-builder, bun-router, crosswind, stx, dtsx, pickier, buddy-bot, logsmith, rpx, ts-cloud, ts-analytics, craft, pantry, better-dx. Plus Stacks itself and Postline.
Per tool
- One-line positioning: what it replaces and who for
- 3–5 post angles — the problem, the before/after, a code snippet, a benchmark or a gotcha it removes
- Assets: screenshot, terminal recording, or a diagram
- Target mix across X, Bluesky, LinkedIn and The OT, with the per-provider variants from the campaign planner
- A companion long-form post on The OT for the ones that deserve one
Sequencing
- Order the tools — don't launch fourteen things in one week
- A standing cadence between launches so the accounts aren't silent in between
- Decide what a "launch" is tied to: a release, a docs milestone, or just readiness
Done when
Each shipped tool has a campaign in Postline — drafted, scheduled, and either published or queued — and the posting cadence runs off the queue instead of ad-hoc.