Dev.to & Hashnode Publishing

Developer blogging platforms offer built-in audiences of hundreds of thousands of developers. This skill covers cross-posting strategy, platform-specific optimization, and building followers on Dev.to and Hashnode.

Before You Start

1. Read .agents/developer-audience-context.md if it exists
2. Decide your canonical URL strategy (important for SEO)
3. Create accounts on both platforms to reserve your username
4. Understand: These platforms reward consistency and engagement

Platform Comparison

Dev.to vs Hashnode

When to Use Each

Cross-Posting Strategy

The Canonical URL Decision

Best Practice: Your Blog + Cross-Post

1. Publish on your blog first — This is canonical
2. Wait 1-2 days — Let Google index your original
3. Cross-post to Dev.to — Set canonical URL to your blog
4. Cross-post to Hashnode — Set canonical URL to your blog

Setting Canonical URLs

Dev.to (in frontmatter):

---
title: Your Title
canonical_url: https://yourblog.com/your-post
---

Hashnode (in editor):

• Click "Article settings" gear icon
• Paste original URL in "Canonical URL" field

Dev.to Optimization

Frontmatter Structure

---
title: "Specific, Keyword-Rich Title (Not Clickbait)"
published: true
description: "One compelling sentence that shows up in previews and SEO"
tags: javascript, webdev, tutorial, beginners
cover_image: https://your-cdn.com/image.png
canonical_url: https://yourblog.com/original-post
series: "Building a CLI from Scratch"
---

Tag Strategy

Rules:

• Maximum 4 tags per post
• First tag is primary (appears in URL)
• Check tag follower count before using

What Performs on Dev.to

Dev.to Engagement Features

Hashnode Optimization

Article Settings

Tag Strategy

Hashnode tags work differently:

• Tags are linked to global topics
• Some tags have dedicated feeds
• Fewer tags, more focused

Popular Hashnode tags:

• javascript, web-development, react
• devops, cloud, aws
• beginners, tutorial
• opensource, programming

What Performs on Hashnode

Hashnode-Specific Features

Content Formatting

Structure That Works

# Title

[Compelling hook — why should they care?]

## Table of Contents (for long posts)
- [Section 1](#section-1)
- [Section 2](#section-2)

## The Problem

[What pain point are you solving?]

## The Solution

[Your approach, with code examples]

### Code Example

// Well-commented code const example = "explained";

## Step-by-Step

1. **Step one** — Explanation
2. **Step two** — Explanation
3. **Step three** — Explanation

## Common Pitfalls

[What to watch out for]

## Conclusion

[Summary + CTA]

---

*If you found this helpful, [follow me](link) for more content about [topic].*

Formatting Best Practices

Building Followers

Consistency Strategy

Engagement Tactics

Bio and Profile Optimization

Dev.to profile:

• Clear profile photo
• Bio with what you write about
• Link to your main site
• List your expertise areas

Hashnode profile:

• Custom domain setup
• Newsletter enabled
• Social links populated
• Blog name and tagline set

Platform-Specific Do's and Don'ts

Do's

1. Do set canonical URLs to protect your SEO
2. Do use platform-specific formatting (embeds, etc.)
3. Do engage with comments within 24 hours
4. Do cross-post to both platforms
5. Do use series for related content
6. Do optimize cover images for each platform
7. Do include a CTA at the end

Don'ts

1. Don't post identical content without canonical URLs
2. Don't ignore comments
3. Don't use only self-promotional content
4. Don't neglect tags — they're discovery mechanisms
5. Don't forget mobile readability
6. Don't publish unfinished drafts
7. Don't keyword stuff your content

Analytics and Iteration

Dev.to Dashboard

Hashnode Analytics

What to Optimize

Tools

Content Calendar Template

Related Skills

• developer-audience-context — Know who you're writing for
• hacker-news-strategy — Drive traffic from HN to your posts
• reddit-engagement — Share posts in relevant subreddits
• github-presence — Link from READMEs to your content
• x-devs — Promote posts on Twitter/X