Content Guidelines

How do we evaluate new sources for daily.dev?

Submitting a new source to daily.dev is a great way to contribute to our community! We welcome your requests and we promise to give proper attention to each and every request. 

How does the review process work?

Step 1 - submit a new source using the daily.dev browser extension (guide)

Step 2 - after submission of your source, your should get updates by email. In the meantime, our team will review it to decide if it’s suitable for our public directory of sources according to the guidelines below.

Step 3 - if the source is approved, we will publish it on daily.dev to all of the users worldwide. Don’t worry, we will keep you posted via email on the results (usually it takes up to one week). 

Anyway, here are a few guidelines to help you understand the criteria of the review process:

What we are looking for?

  1. Relevant and fresh content for developers.
  2. Sources that are generating exciting and professional content.
  3. Sources that publish new content regularly (at least once a week).
  4. Sources that have published a substantial amount of content to date.
  5. Sources about innovative and trending topics that will inspire our community.
  6. Good vibes ✌️

When will we reject a source request?

  • It is not publishing content for developers.
  • It is a personal blog (global thought-leaders excluded).
  • It is used mostly for self-promotion.
  • It is not publishing content written in English.
  • It was not active in the past three months or more.
  • It doesn't provide an RSS feed available for public use.
  • It is publishing politically-oriented content.
  • It includes content that is either illegal, pornographic (including mature in content or overtly sexual), racist, sexist (or otherwise offensive), grotesque (or obscene), inflammatory, and other inappropriate content.

❗️ Please note that we kindly ask you not to share copyrighted or trademarked sources. If you did not create the source you are submitting for review, make sure it's publicly accessible for sharing. We will give due credit to the owner.

Be respectful to the community

The daily.dev community is highly sensitive to content quality and the code of conduct of publishers. After a new source is approved and added to the daily.dev feed, we continue to monitor it continuously. Our aim is simple -- to maintain and enforce the content guidelines for the benefit of our community.


We kindly ask you to refrain from misusing the opportunity to be featured on the daily.dev feed.

How to get your article picked up by daily.dev? [For indie bloggers]

As mentioned above, we don't accept personal blogs at the moment. HOWEVER, there are three ways for you to get your article picked up by daily.dev:

1. Publish guest articles on well-known publications that are already included in the source list of daily.dev. You can explore the list using the sidebar in the app itself. There are plenty of options out there.

2. Publish articles on developer blogging platforms such as Hashnode, DEV.to or Hacker Noon. If your article will gain enough traction on those platforms, there's a high chance it will be picked up by daily.dev as well.

3. Submit a new and original article to daily.dev/blog. Here's the process of how to submit a story to our blog. Please read the instructions carefully before submitting a guest post.

Some legal stuff...

Daily Dev Ltd. does not claim ownership or copyright to any of the submitted sources. If a copyright infringement claim is made regarding the submitted source, the content will be removed and the submitted user might be blocked from future submissions. Read more about our Privacy Policy and Terms of Service.