DEV Community

Ioannis Apostolou
Ioannis Apostolou

Posted on

Dev.to or your own blog

Hello!

I want to start write blog and I have been creating a project where is blog and portfolio page together (you can see the project at gitlab)

But I love to read articles in dev.to, and I want your thoughts.
It's better to write in dev.to? In your own domain (your website)? Or in both and why?

What is your opinion about that?

Thank u!

Discussion (14)

Collapse
inhuofficial profile image
InHuOfficial

As someone who started writing on DEV here is a suggested route:

  1. Write on DEV first and get into a rhythm / find your style
  2. Set up your own blog (I am at this step)
  3. Post to your own blog first, 1 week later post the article to DEV and set the canonical URL to your own blog.

That should maximise your chances of getting the link juice and your own blog ranking above the DEV version in Google.

You want to control the blog so you can build a mailing list as “the power is in the list” is the oldest and most important digital marketing rule. Controlling your mailing list allows you more flexibility and opportunities once you have grown to a reasonable size.

Collapse
giannistolou profile image
Ioannis Apostolou Author

Thanks a lot of for your advice! When u deploy your own blog will u add all your old dev.to aricles or your blog will have only new articles?

Collapse
inhuofficial profile image
InHuOfficial

I am going to grab a few of the better articles for the blog, but as my intention is to write some stuff that isn’t DEV content (and the occasional DEV only post) I won’t be copying everything across.

Thread Thread
giannistolou profile image
Ioannis Apostolou Author

Oh i understand thank u!

Collapse
vishnusathasivam profile image
VISHNUSATHASIVAM

But there is no option to send the content from my blogspot to Gut hub. It is also strange to see that I could not see my blog from other smart phones. Please clarify.

Collapse
mrbeanguy profile image
Bean

Hey there,

I have a great suggestion for ya! Did you know you can use dev.to and it can be pushed to your domain like a blog? This is a service offered by dev.to in the settings area! This is all ran by a program called StackBit!

Collapse
mrbeanguy profile image
Bean
Collapse
giannistolou profile image
Ioannis Apostolou Author

Oh, i didn't know that! Thank u!

Collapse
recursivefaults profile image
Ryan Latta

My answer is that it depends on what your long-term goals are.

If you're thinking of this as a short-term thing like caputring your journey building stuff for a bit, start with dev.to and move your content to your own.

(By the way, you can build your own free blog using github pages, and Jekyll which is seemless with dev.to)

Now, if you're considering long-term benefits with a content strategy you'll want to own your own platform. Publish there first and syndicate back here. Thats what I do. Dev.to supports that as well.

Collapse
vishnusathasivam profile image
VISHNUSATHASIVAM

Please explain owning platform. If is a great thing.

Collapse
recursivefaults profile image
Ryan Latta

Ok, lets take two examples.

Rented Platform (Facebook or other Social Media, Medium, Dev.to):

You publish your content on these platforms, but the audience you reach is controlled and managed by them. If they change their rules or pricing or decide to remove you, you lose your audience. This has happened repeatedly with larger media sites.

Owned Platform (Hosted Wordpress or Blog, Newsletters):

You build your audience on services you own. While you work harder to get each person to look at your content or join you, you have control over what reaches them and how. You want to send them all a new piece of content, you can precisely control who gets it and when. If you want to eventually let them know of something new that you're selling, you can tell them all easily without worrying if everyone gets the same message at the same time.

Collapse
giannistolou profile image
Ioannis Apostolou Author

Thanks a lot for the informations!

Collapse
blaisep profile image
Blaise Pabon

These are all good suggestions.
I would like to add a little twist.
Consider having all your own content under source control, like a git(lab) repo. Then use CI pipelines to push content to your various channels, adding formatting and SEO as needed.
Keeping your content in a single, local place makes it easier to index for your own use, and possibly cross reference with your bookmark history, photo albums, etc.
Similar to talkpython.fm/episodes/show/299/pe...

Collapse
vishnusathasivam profile image
VISHNUSATHASIVAM

Yes. It is a good idea. I am blogging for the last 12 years. The blog is not inspiring and need development. Please do something about it.