Publish and optimize technical content on Dev.to & Hashnode

This skill covers cross-posting strategy, platform-specific optimization, and follower building for publishing on Dev.to and Hashnode, two developer blogging platforms with built-in audiences. Dev.to has roughly 10M+ monthly visitors, is subdomain-only, has no native monetization, strong community reactions and comments, and a broader, more-beginner audience. Hashnode has roughly 3M+ monthly visitors, a free custom domain so the writer's own domain gets the SEO, a built-in newsletter and sponsor program, and a more senior, focused audience. Before starting, it checks for a .agents/developer-audience-context.md file, has the writer decide a canonical-URL strategy, and recommends reserving a username on both platforms early, since these platforms reward consistency and engagement.

Use it whenever the user wants to publish on Dev.to, Hashnode, or another developer blogging platform - trigger phrases include "Dev.to," "Hashnode," "developer blog," "cross-posting," "technical blogging," "canonical URL," or "developer content platform." Favor Dev.to when maximum reach or community engagement is the priority, content targets beginner/mid-level readers, or there is no personal blog yet; favor Hashnode when building a personal brand, wanting custom-domain SEO, building an email list, or supplementing an existing blog. The recommended sequence is to publish on the writer's own blog first (canonical), wait 1-2 days for Google to index it, then cross-post to Dev.to and Hashnode with the canonical URL set back to the original - never publish identical content on multiple platforms without setting that canonical URL.

Input is a piece of technical content plus a target platform. Output is a platform-formatted post: on Dev.to, YAML frontmatter with title, published flag, description, up to four tags (the first tag is primary and appears in the URL), cover image, canonical_url, and an optional series, for example:

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

On Hashnode, article settings are configured through the editor - subtitle for SEO keywords, a 1600x840 cover image, an SEO title and description capped at 155 characters, canonical URL, and table of contents enabled for long posts. The recommended structure is a hook, an optional table of contents, a problem section, a solution section with code examples, numbered steps, common pitfalls, and a conclusion with a call to action; posts of 1000-2500 words perform best, with short 2-3 sentence paragraphs and liberal use of lists.

For Dev.to, high-follower tags include #javascript (200K+), #webdev (150K+), #beginners (120K+), #tutorial (100K+), #react and #programming (80K+ each), #python (70K+), and #devops/#opensource/#productivity (40-50K+); beginner tutorials, listicles, career advice, and hot takes perform best there. For Hashnode, popular tags include javascript, web-development, react, devops, cloud, aws, beginners, tutorial, opensource, and programming; in-depth tutorials, architecture posts, and DevOps/cloud content perform best, while listicles perform worse than on Dev.to. Analytics differ too: Dev.to reports views, reactions, comments, reading time, and followers-from-post; Hashnode reports total views, unique visitors, read ratio, time on page, referrers, and newsletter signups. Recommended tools: Octolens for monitoring both platforms for mentions and trends, Hemingway Editor for readability, Carbon for code screenshots, Unsplash and Canva for cover images, and Grammarly for proofreading. Related skills: developer-audience-context, hacker-news-strategy, reddit-engagement, github-presence, and x-devs for driving traffic to the published posts.

Each platform has its own engagement surface. Dev.to reactions (heart, unicorn, saved, fire) carry different meanings, replying to every comment gives an algorithm boost, the #discuss tag suits opinion or question posts, and Listings can post jobs, events, or products. Hashnode adds custom CSS for a unique blog look, widgets for GitHub or newsletter CTAs, a sponsor program, and analytics that go deeper than Dev.to's. The skill's engagement tactics for building followers are: reply to every comment (algorithm boost plus relationship building), comment on others' posts (visibility and community), follow relevant authors (often reciprocated), share on social media (external traffic), link between your own posts (keeps readers on your content), and create series (encourages following for updates) - backed by profile basics (a clear photo, a bio naming what you write about, and a link to your main site on Dev.to; a custom domain, enabled newsletter, populated social links, and a set blog name/tagline on Hashnode). When a post underperforms, the skill's fixes are: low views - better title or different tags; low reactions - a more engaging opening; low comments - end with a question; high bounce - better structure or hook; low followers - a stronger CTA or a series.

Developers and technical writers deciding where and how to publish technical content, cross-post it without hurting their own site's SEO, and grow a following through consistent, platform-tuned posting and engagement - the skill notes that 4+ posts a month drives rapid follower growth, 2-3 a month steady growth, 1 a month slow but sustainable growth, and sporadic posting gives minimal retention. Its core do's are: set canonical URLs, use platform-specific formatting, engage with comments within 24 hours, cross-post to both platforms, use series, optimize cover images per platform, and end with a CTA; its don'ts are: never post identical content without a canonical URL, never ignore comments, avoid purely self-promotional content, don't neglect tags, don't forget mobile readability, don't publish unfinished drafts, and don't keyword-stuff.