Automating blog publishing to dev.to and LinkedIn
Writing an article is already work. Republishing it manually on dev.to — copy-pasting the markdown, reformatting code blocks, fixing relative links — then crafting the LinkedIn post with the image ...

Source: DEV Community
Writing an article is already work. Republishing it manually on dev.to — copy-pasting the markdown, reformatting code blocks, fixing relative links — then crafting the LinkedIn post with the image and hook text... that's exactly the kind of friction that ends up meaning you post once every two months. The goal was simple: node scripts/publish-article.js my-slug and done. Here's what that looks like in practice. The 3-script architecture Three Node.js scripts, each responsible for one platform or step: devto-draft-all.js + devto-publish-next.js — dev.to pipeline with cadence (4 days between articles) linkedin-publish.js — LinkedIn publishing with large image publish-article.js — unified script that orchestrates everything Each pipeline has its own JSON schedule file, following the same pattern as posts.json: a list of objects with slug, scheduled publication date, and status (draft, published). Simple, versionable, readable. Dev.to: the easy API Dev.to exposes a clean REST API. An API k