5
8 Comments

Do you blog on Dev(.)to or Hashnode?

Torn b/w which dev blogging platform I should invest my time on. Anyone have any experience with either?

I'm currently leaning towards Hashnode because it looks trivial to route through a custom domain, but Dev.to (as well as Hashnode) makes it easy to set a canonical metatag linking to the original.

My motivation for publishing on these platforms is to engage with their audience.

What platform do you like more?
  1. Dev.to
  2. Hashnode
Vote
posted to Icon for group Developers
Developers
on October 11, 2020
  1. 3

    Neither. I use Github Pages (I'd also recommend Netlify) and host your own.

  2. 2

    I wrote an article on each to see if a backlink would affect my domain authority. It didn't seem to.

  3. 2

    I have both, currently linked my domain to Hashnode blog https://ideaman.io . Its very easy to link your domain. The only thing I hate about Hashnode is their like buttons (with medium you have one like/clap button) with Hashnode user get 20 options to express their support, that looks ugly to me.

  4. 2

    I haven't looked at Hashnode beyond scanning the landing page, yet, but I'd classify Dev as more of an open source social network that features blogs, rather than a blogging platform per se. They've given a decent amount of thought to on-boarding, and they seem to do a good job of acknowledging that a lot of developers are going to already have a blog and want to just get their content to a new audience, in their case through RSS and links back home. They also have some nice custom templating commands for internal and repository hyperlinks.

    I haven't been writing enough technical posts to push much their way, but I've been happy giving the site a couple of minutes every morning and yanking the occasional programming article off my blog for re-use there.

    Now giving Hashnode a couple of minutes without signing up, it looks much more like just a straightforward blogging platform. The red flag (to me) is the comments. Every platform obviously has a spam problem (and Dev had a rough week with spam posts), but the rare comments I saw on Hashnode were either (paraphrasing, of course) "you clearly just hate (language/platform/framework/library)" or "I enjoyed learning a lot about (insert post title...or don't, if the script failed)."

    So, I probably wouldn't like it, there, since I already have a blog that I'm happy with (and can get away with posting about what I'm reading), but that doesn't mean that you won't like it.

  5. 2

    I'm doing content syndication on both, Dev.to and Hashnode with my blog: https://www.indiehackers.com/product/box-piper, https://boxpiper.com/
    Dev.to proves to be more worthy and Hashnode is not providing enough traction right now.
    In my opinion, Hashnode works brilliantly for those who already has an existent followers and take lot of time to build community.

  6. 2

    Don't have any experience with Hashnode, but can highly recommend dev.to. It's really easy to cross-post content from your personal blog and community is very nice and engaging. Feel free to follow me there as I'm planning to blog more regularly soon: https://dev.to/clarity89.

  7. 9

    This comment was deleted 5 years ago.

    1. 5

      Totally agree with this. I take part on Dev.to and really love the community there, but honestly, everything should eventually go back to a home you own.

      I mean no offense to any 3rd party site, but controlling your destiny has to come first, and that means controlling the definition of home.

      1. 2

        This comment was deleted 2 years ago.

        1. 2

          I recently signed up on hashnode to take a look at it, my reason being it never hurts to see what is out there. I don't feel it's as comfortable an environment compared to dev.to. For the record, I'm not saying that to suck up to dev.to.

          I do the same thing @mishacreatrix I post to sites but make it as clear as I can that it came from my home site originally.

          1. 2

            This comment was deleted 2 years ago.

Trending on Indie Hackers
I got my first $159 in sales after realizing I was building in silence User Avatar 42 comments I spent more time setting up cold email than actually selling. Here is what fixed it. User Avatar 40 comments I just wanted to taste AI coding tools. A week passed. User Avatar 27 comments I got tired of rewriting the same content for 9 different platforms. So I built Repostify. User Avatar 25 comments A pattern I keep seeing in EdTech: traffic isn't usually the problem. User Avatar 21 comments Three Days Before Launch, I Let My Own Tool Tear Me Apart User Avatar 19 comments