This article provides a step by step guide to publishing one markdown article to dev.to, Medium, AWS Builder Center and LinkedIn with publishing-ki...
For further actions, you may consider blocking this person and/or reporting abuse
I wonder: is the agent part necessary? Wouldn't you achieve the exact same thing with Playwright or any other browser automation framework?
the playwright approach will work - but then you have to manage the install and system dependencies. The Claude Chrome integration is well integrated into Claude Code and is turned on by standard claude flags
On one side, you have deterministic results with a few added dependencies. On the other side, you have chances of not having the desired outcomes and tokens to spend (aka, money).
I personally know what I choose.
more than one way to skin a cat.
I am a believer of going with whatever tools work best for
you. no two use cases are exactly the same.
I just started a Substack account too. Worth adding to the comparison table. Substack has no public posting API either, same as Medium. It only gives read-only RSS feeds. A fifth destination would need the same browser-paste approach as Medium and Builder Center.
I will take a look at substack- I don't usually post there but can't hurt too lob out a few articles.
We run this pipeline by hand every week — one source post, a dev.to cross-post, Hashnode and Medium mirrors on Sundays — and your table matches our scars. Medium's API going closed is what killed auto-mirrors for everyone; LinkedIn being the odd one out is why our LinkedIn post is a rewrite, never a copy. The trap nobody warns about is canonical drift: the canonical_url has to stay the bare origin URL or the SEO credit splits across destinations. Does publishing-kit pin canonical per destination, or does it trust whatever the frontmatter says?
Good point. I haven't focused on what happens to the canonical URL- putting this on my to-do list
Nice workflow. One thing I enjoyed is that you focused on portability and ownership of content rather than locking the process into a single platform. Keeping Markdown as the source of truth makes future migrations and cross-posting much easier. This is the kind of practical productivity improvement that compounds over time.
Very cool, will try this soon-ish!
solid read
this writing explanation helped, thanks
very useful, thanks