Developer Marketing as a Build Artifact

Description and use

Small teams ship code but rarely publish marketing content. An automated pipeline using LLMs for drafts and API publishing, with human approval, enables quick, high‑quality releases across platforms.

Problem

Small teams ship code but rarely publish marketing content, leaving features unannounced to users.

Outcome

Automating the mechanical parts of developer marketing while keeping human approval prevents spam, ensures quality, and provides measurable engagement metrics.

Workflow

• Detect a new release via webhook
• Generate draft post using LLM from diff, changelog, and context
• Place draft in review queue
• Human reviews and approves or rejects
• On approval, schedule cross‑post to Dev.to, Hashnode, Medium, Bluesky, Mastodon, WordPress, Buttondown or blog repo
• Set canonical URL on original post
• Publish to each platform with platform‑specific formatting and UTM tags
• 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.

Source