Shipping in Silence: Treating Developer Marketing as a Build Artifact

Description and use

An automated marketing pipeline that drafts posts from repository activity, queues them for human approval, and publishes across multiple platforms with canonical URLs and engagement tracking.

Problem

Small teams ship code but rarely publish marketing content, leaving releases unnoticed by users.

Outcome

Automated pipeline reduces manual effort, ensures timely marketing content, and provides metrics for continuous improvement.

Workflow

• Detect repository event (commit/release) via webhook
• Generate draft post using LLM from diff and changelog
• Place draft in review queue for human approval
• On approval, schedule cross‑post to Dev.to, Hashnode, Medium, Bluesky, Mastodon, WordPress, Buttondown or blog repo
• Set canonical URL on original post and add UTM tags
• Publish to each platform respecting format limits and timing
• Track views and engagement via platform APIs

Evidence

Drafting stopped being the bottleneck. A capable model given a diff, a changelog and some product context produces a serviceable first draft of a release post.

Source

Publishing became an API problem. Dev.to, Hashnode, Bluesky, Mastodon, Medium, WordPress and Buttondown all take programmatic writes.

Source

Herald is a working implementation of this. It watches project repositories, drafts posts from real commit and release activity, parks them in a review queue for a human, then publishes on a schedule to Dev.to, Hashnode, Bluesky, Mastodon, Medium, WordPress, Buttondown or a commit to your blog repo.

Source