How posting to dev.to works
dev.to is a longform destination in Bangers. You share a thought (a voice note, a technical update, a longer brief about something you've been working on) and the team drafts a full article in your voice: a title and a body with subheads. You review it, revise it if you want changes, and approve it. Once approved, it publishes to your dev.to account on schedule.
That makes dev.to a natural fit if part of the business is technical writing: a product update explained for other developers, a lesson learned while building something, a walkthrough. The same underlying thought can also become a shorter post somewhere else, but dev.to is where it gets the room to actually explain itself.
What Bangers knows about dev.to
dev.to has no hard character limit in Bangers. It follows the longform playbook: a title under 100 characters and a body of 500 to 1,200 words with subheads, written as a real article.
If a draft heading to dev.to ever arrives as a shorter plain note instead of a full piece, Bangers still publishes it by splitting the first line off as the title and posting the rest as the article body, the same heuristic it uses for WordPress and Ghost.
dev.to doesn't support threads. There's no chained-post format there, so a thread draft is rejected with a clear reason instead of being forced into something dev.to can't represent.
dev.to publishing through Bangers doesn't currently attach images: no generated image, and nothing you upload yourself through Telegram. The article publishes as title and markdown body only.
Articles publish live directly once you've approved them, with no separate draft stage inside dev.to itself. Bangers is where the review happens.
Connecting it
Connecting dev.to takes one field: an API key.
Generate it from your dev.to account: go to Settings → Extensions → Generate API Key, and paste the result into Bangers. There's no separate username or site URL to enter: the key alone is enough for Bangers to identify your account and publish under it.
Bangers checks the key against dev.to before saving it, confirming which username it belongs to, so an invalid or expired key is caught immediately instead of failing at publish time.
The API key is tied to your dev.to account rather than to Bangers specifically, so you can revoke it from the same Extensions screen at any point. Once revoked, the next publish attempt fails with a clear reason instead of silently going nowhere, and reconnecting just means generating a fresh key and pasting it back in. If you manage articles across more than one dev.to account, each needs its own key and its own connected channel.
When it fails
Nothing publishes without your approval first. If the actual publish to dev.to fails afterward (the API key was revoked or expired), you're notified in Telegram within a minute with the specific reason, and you can retry from there.
Frequently asked questions
Does Bangers publish full dev.to articles, or short posts? Full articles. dev.to is treated as a longform destination: a title under 100 characters and a 500 to 1,200 word body with subheads, published as markdown.
What do I need to connect dev.to? Just an API key, generated from your dev.to account's Settings → Extensions → Generate API Key screen.
Can Bangers add an image to a dev.to article? Not currently. dev.to publishing through Bangers is title and markdown body only, with no image attached, generated or uploaded.