Blog
A draft that already fits the room
One source becomes a Dev.to essay, a Reddit post, a Hacker News title, or a short thread. You copy it and paste it from your own account.
A changelog line is one fact. Dev.to wants the essay. Reddit wants the useful part in the body. Hacker News wants a title and a first comment. X wants one idea per line. Paste the same paragraph into all of them and the rooms that were worth joining will treat you like a feed.
ProductPost 360 writes those versions from the source you already published. The first three channels are drafted when you open the source. Every other room waits until you tap it. You still read the draft, and you still paste it.
One source, three shapes
ThinkReview’s comparison, “Grok Bot vs Claude Desktop,” is one blog post. The Dev.to draft is the long version: a title, a markdown body, tags, and a canonical URL pointed back at the original. Article sites can carry the whole piece. Your page stays the one search should rank.
The same release notes, opened on Reddit, are a different object. v2.3.10 was a sidebar bug on Azure DevOps Server. The draft leads with the bug, names the host, suggests subreddits, and keeps a media URL for the release image. A discussion room will remove an announcement. It will often keep a fix someone on that host can use.
X is the short room. The draft is a thread, one tweet per line, plus the image. LinkedIn is the professional retelling of the same split: what changed in the work, in a few sentences a colleague can forward. Hacker News is a title, the URL, and an optional first comment that states the trade-off. You do not need all of them this week. You need the shape before you start typing.
Three drafts, then the room you mean
The source opens with three channels drafted. The rest of the list is a tap. That limit is the point. A tutorial belongs on the hub that wants steps. A pricing change belongs in a builder thread. A bugfix with nothing a stranger can reuse stays on the changelog.
Forums on the left of that screen are the niche rooms: a cloud community, a framework forum, a group that already talks about the job. Turn one on when the source fits that room. Leave the others for a later ship.
Two controls sit under the draft.
- Remix asks for another angle on the same source. Use it when the facts are right and the opening is wrong.
- Regenerate writes the draft again. Use it when the draft missed the release.
Read either result before it goes anywhere. The draft has the source and the room’s usual shape. You have the tone of that community, and you are the person who will be in the thread tomorrow.
Paste it, then mark it posted
Each draft has Copy MD and Copy Rich, and a link that opens that site’s composer. Copy the text. Paste it from your account. Accounts that auto-post get removed, which is why the product stops at the draft.
Mark as posted when the link is live, so tomorrow’s queue does not offer you the same paste again. Then wait. The same text in five communities on the same afternoon is a pattern moderators already know. A late post in the right thread beats an early one that gets removed.
If the draft is still useful with the link deleted, it is ready. If it is only an announcement, leave it on the changelog and ship the next thing.