DEV Community

Discussion on: Dev.to or your own blog

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
giannistolou profile image
Ioannis Apostolou Author

Thanks a lot for the informations!

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.