How to cross-post an article to DEV Community

Publish a Markdown article on dev.to natively or with Postbean. Check canonical links, code blocks, tags, covers and announcement timing.

Published Updated devto, cross-posting, how-to
Illustration: How to cross-post an article to DEV Community

Cross-posting to DEV means publishing an article, not dropping a social caption into a longer text box. Bring the explanation, code and prerequisites with you. If the piece originally appeared on your own site, also decide how you will identify that original source.

DEV has a native Markdown editor, scheduling and a canonical-URL field. Postbean can send a Markdown article at a scheduled time and keep its shorter social announcements nearby. Choose the route based on the fields you need, then inspect the article where readers will actually see it.

Prepare a version that works outside your site

Start with an article you own or are authorized to republish. Read it without your website’s sidebar, previous installment or embedded download widget. Add the context a DEV reader needs to follow the procedure from that page alone.

For a technical tutorial, list the relevant environment and prerequisites before the first command. Include expected output or an explanation of what a successful step changes. A screenshot of a command is harder to reuse than a text code block, so preserve the actual code where possible.

Keep the title, source URL, tags, cover and article body in a working document. Separate publication metadata from the Markdown body. A website-specific frontmatter block pasted into the body is not necessarily how the destination expects those fields.

Publish or schedule natively on DEV

  1. Select Write a Post, add title, body and tags, then save a draft.
  2. For a republication, open the settings control and enter the original page in Canonical URL. The basic editor uses its canonical_url frontmatter field instead.
  3. To schedule, open Schedule Publication through the control near Publish and choose the date and time.
  4. Review the saved item and preview.

DEV’s writing and scheduling help describes the local-time scheduling flow. Its editor guide documents the canonical field and a maximum of four tags. A canonical identifies the original version; do not turn that setting into a promise of search ranking.

Connect DEV Community to Postbean

Sign in to the DEV account that should author the article. Open Settings, then Extensions, and generate a DEV API key. In the intended Postbean workspace, open Connections, choose DEV Community and enter that key.

This connection uses DEV credentials in a form, not an OAuth redirect. Postbean validates the key against the DEV account endpoint. Check the username returned before starting the article. The DEV key is not interchangeable with a Postbean API key used for automations.

Keep it out of Markdown examples and shared screenshots. If you revoke the DEV key, generate a replacement and reconnect before the next scheduled send. A saved article cannot authenticate itself after its connection credential has been revoked.

Prepare the article in Postbean

1. Give DEV its full body

Open Create post and select DEV Community. Use the caption area for the Markdown article, including headings, links and fenced code blocks. Postbean sends that text as the article body, not as a short teaser that automatically expands into the original webpage.

Postbean does not set a channel-specific caption maximum for DEV, but the panel’s shared caption is limited to 5,000 characters by the save endpoint. For a longer article, use DEV’s native editor or put the full body in DEV’s network-specific caption while keeping the shared text within that limit. DEV’s own validation and content rules still apply. The Forem article API is the destination contract, and DEV makes the final acceptance decision.

If you also select Bluesky or LinkedIn, write separate shorter versions for them. A code-heavy Markdown article is not a useful caption on every feed. Use the social version to name the problem and invite readers to the full article once its URL exists.

2. Supply an explicit title

The panel composer has no dedicated DEV title input and does not submit a post title. Put the intended headline on the first line of the effective DEV body, without a Markdown heading marker: the publisher uses that line as its fallback title, capped at 120 characters. It also remains in the article body. If you need a separate title without that repeated line, use DEV’s native editor; REST integrations can supply the post’s title field explicitly.

Choose a title that tells a reader what they will accomplish or understand. “Trace a slow query before adding an index” is clearer than a broad claim about mastering database performance. If the procedure depends on a specific environment, name it where readers will notice.

3. Check code and image references

Preserve opening and closing code fences and use the appropriate language label. Read the rendered result later to confirm that quotes, indentation and line breaks survived. A source article that looks correct in your editor can still rely on syntax or embeds that need adjustment at the destination.

For inline images, use public references that will work outside your private workspace. The cover attachment is a cover, not an automatic carousel of inline illustrations. If a diagram is essential between steps, include and check its place in the body.

Postbean supports a cover image and accepts JPEG, PNG or WebP uploads up to 8 MiB. It does not upload native video or publish a first comment on DEV. Place essential references in the article rather than planning to recover them through an automated reply.

4. Choose up to four useful tags

The DEV publisher takes up to four tags, lowercases them, removes non-alphanumeric characters and duplicates, and keeps the resulting list. Put the important topics first. A label whose punctuation carries meaning can change during normalization, so inspect the published tags.

Do not confuse organizing tags inside your workspace with the destination’s topic conventions. Review what the selected labels become on DEV. A tutorial about a database query does not need a tag for every tool mentioned in a footnote.

5. Decide the canonical workflow before scheduling

The backend publisher can carry a canonical URL when configured, but that does not establish a visible canonical input in every panel workflow. Do not assume such a field exists in the composer. If setting the canonical before publication is essential, use DEV’s verified native editor route for that article.

You can still use Postbean for the social announcements. Keep the original public URL available and check DEV’s article settings after publication where appropriate. This separates a supported backend capability from an editor control you have not confirmed.

6. Set the article time before the teaser

Save a draft and choose the schedule in the workspace timezone. For a new DEV article, publish it before scheduling a teaser that needs its final URL. Do not invent the URL from a working title and assume it will resolve.

Once the article is live, open it, copy the actual link and add it to the shorter versions. Use per-network scheduling for their timing. If the article needs correction, fix that before sending readers to it.

Common errors and final checks

If connection fails, verify the DEV key and account rather than trying an OAuth login. If the title is wrong, check whether the publisher used its fallback. If the tags changed, inspect normalization and order before adding more labels.

If code formatting breaks, compare the rendered blocks with the source and test the commands as a reader would. If the article publishes twice, check whether native scheduling, RSS import or another integration was already responsible for the same piece before retrying.

Postbean does not sync DEV article metrics. Check readership and reactions on DEV; missing numbers in Postbean do not mean nobody read it. Open the cover, canonical setting, links and code before sharing the next announcement. The DEV channel guide is the reference for supported publishing behavior.

Example: verify the tutorial from a clean start

For an invented setup guide, follow the published commands in a fresh example project rather than relying on your existing environment. Confirm that every referenced file, prerequisite and expected result appears in the article. Check that the canonical URL names the original article, not the blog homepage. Then write the social teaser from the problem the tutorial solves, using its actual published URL.

Sources

Write it once. Publish it everywhere.

Connect your networks and schedule your first post in a few minutes. Free plan, no card.

Create your free account