Connecting DEV Community to Goji

DEV Community — dev.to — is where a great many developers read. If you write anything technical, republishing there puts it in front of an audience that is already looking for it. As with Medium, every post is published with a canonical link back to your own site, so the copy supports the original rather than competing with it.

What connecting DEV gives you

• Automatic republishing. Each new article becomes a DEV post with its title, body and cover image.
• A canonical link. Search engines keep treating your own site as the original.
• Tags carried over. Article tags become DEV tags, which is how readers there find anything.
• Draft or publish. Post immediately, or create drafts to review before releasing.

Before you start

You need a DEV account and an API key from its settings. Nothing needs approval and there is no developer programme to join.

How to get the API key

1. Sign in to dev.to.
2. Open Settings → Extensions.
3. Find the DEV Community API Keys section.
4. Enter a description such as "Goji" and generate the key.
5. Copy it — treat it like a password, since it can post as you.

How to connect it in Goji

1. Open Channels and choose DEV Community.
2. Paste the API key.
3. Choose whether posts should be published or created as drafts.
4. Save. The key is checked with DEV immediately.

About tags

DEV allows up to four tags on a post, and they must be plain lowercase words with no punctuation. Goji cleans your article's tags to fit that rule and uses the first four. If your tags are phrases, expect them to be shortened — it is worth adding a few simple ones such as webdev or php to the articles you plan to republish.

If something goes wrong

• The key is rejected. It was copied incompletely, or it was revoked in DEV's settings. Generate a new one.
• The post appeared without tags. None of the article's tags survived cleaning. Add simple lowercase tags.
• Nothing appears on my profile. The channel is creating drafts — check your DEV dashboard.
• Formatting looks wrong. DEV renders Markdown; unusual HTML may be simplified.

Writing articles that suit DEV

DEV rewards specificity. Posts that explain a concrete problem and the code that solved it are read; general marketing posts are quietly ignored and sometimes reported. If you publish a mix of technical and commercial writing, it is worth using publishing rules so only the technical articles reach this channel.

A cover image helps more here than on most networks, because DEV shows it at full width at the top of the post and in every feed listing. Articles without one still publish and simply appear with a plain title card, which is easy to scroll past.

Common questions

Will this count as duplicate content? Not with a canonical link, which is always set. DEV supports canonical links precisely for this.

Can I edit a post after it is published? Yes, on DEV, like any other post.

Is there a limit? DEV applies its own rate limits; ordinary publishing is nowhere near them.

Should everything go to DEV? No — it is a developer audience. Sending unrelated marketing posts there tends to be ignored, and may be reported.