# Where to Publish Content? ![rw-book-cover](https://readwise-assets.s3.amazonaws.com/static/images/article1.be68295a7e40.png) URL:: https://dev.to/maxkatz/where-to-publish-content-53ao Author:: dev.to ## Highlights > My recommendation is almost always to publish first on your own personal blog. There are a number of reasons for that: > It allows you to build your portfolio and keep all your work in one place > It allows to build your personal brand > It can act as your “second” resume as it shows that you actually published. It’s easy to put anything on a resume. A blog shows the actual work > When you get a new job, the content you published will be available on your personal blog and not on the company’s blog ([View Highlight](https://instapaper.com/read/1416593161/16552695)) > Dev.to is a great community for developers. Dev.to allows you to syndicate or re-publish content from your blog. It even automatically imports content from your blog and keeps the content in draft mode. ([View Highlight](https://instapaper.com/read/1416593161/16552699)) > LinkedIn Publishing is a great platform for publishing content but doesn’t allow importing existing content or allowing you to set the cononical URL manually. If you want to re-use existing content but don’t want to simply copy and duplicate it, one option is to write a new introduction paragraph on LinkedIn and then link back to the original article. ([View Highlight](https://instapaper.com/read/1416593161/16552702)) > If your company will allow this, first publish content on your personal blog and then syndicate content on the company’s blog. ([View Highlight](https://instapaper.com/read/1416593161/16552706)) --- Title: Where to Publish Content? Author: dev.to Tags: readwise, articles date: 2024-01-30 --- # Where to Publish Content? ![rw-book-cover](https://readwise-assets.s3.amazonaws.com/static/images/article1.be68295a7e40.png) URL:: https://dev.to/maxkatz/where-to-publish-content-53ao Author:: dev.to ## AI-Generated Summary None ## Highlights > My recommendation is almost always to publish first on your own personal blog. There are a number of reasons for that: > It allows you to build your portfolio and keep all your work in one place > It allows to build your personal brand > It can act as your “second” resume as it shows that you actually published. It’s easy to put anything on a resume. A blog shows the actual work > When you get a new job, the content you published will be available on your personal blog and not on the company’s blog ([View Highlight](https://instapaper.com/read/1416593161/16552695)) > Dev.to is a great community for developers. Dev.to allows you to syndicate or re-publish content from your blog. It even automatically imports content from your blog and keeps the content in draft mode. ([View Highlight](https://instapaper.com/read/1416593161/16552699)) > LinkedIn Publishing is a great platform for publishing content but doesn’t allow importing existing content or allowing you to set the cononical URL manually. If you want to re-use existing content but don’t want to simply copy and duplicate it, one option is to write a new introduction paragraph on LinkedIn and then link back to the original article. ([View Highlight](https://instapaper.com/read/1416593161/16552702)) > If your company will allow this, first publish content on your personal blog and then syndicate content on the company’s blog. ([View Highlight](https://instapaper.com/read/1416593161/16552706))