daily.dev is a community of developers getting together around discovering and exploring dev news. We are so happy to see you interested in taking an active part in the quest to empower developers' professional growth worldwide.
Before you start 🙏🏼
First, we want to sincerely thank you for showing interest in submitting a story to daily.dev. That’s it. Now we can move on.
In this post, we will outline the steps required to have your story be co-published on daily.dev blog, as well as other publications and social media. Follow daily.dev on Twitter (@dailydotdev) and on DEV publication to help us share your content and reach a broader audience. By subscribing, you will help our community of developers, which we hope you feel belong to.
How to submit a story 🤔
- Please email us at firstname.lastname@example.org with a link to your draft story in DEV. You must share a draft link and wait to publish the story. Once you finished writing, click “Save Draft” and send us the URL.
- If it is the first time for you to write a post on DEV, here is how to do it and how to use their editor (Editor Guide).
- Our team will review your story. We commit to giving you the first feedback within three days. Since we care about content quality, we might be in touch with you to fine-tune your story to maximize it’s potential.
- If your story is approved, we will add you as a contributor on our DEV publication. Once done, you can publish your post to our publication.
- Well done! Now it’s time to share your story everywhere. See below “What happens after we approve your story.” 👇🏽
How to format your draft before submitting for review 📑
Every draft submitted must use basic Markdown to write and format the syntax of your story. It is the way for our blog platform to identify how you intended to format your story. In case you’ve written for other blogging platforms, you might already be familiar with Markdown syntax.
In case Markdown is entirely new to you or if you want to learn about it, check out this cheat sheet. Anyway, we’d be glad to support you in the writing process. In case you couldn’t find an answer in this Markdown guide, please contact our support. Important Note: Make sure you contact us for Markdown issues only after you’ve already finished writing and polishing your story.
What must be included in your email 💌
Your story URL posted as a draft in DEV. Your article must include:
- Cover Image. You can make your own or buy one. Otherwise, please pick an image from either: Pexels, Pixabay, or Unsplash.
- Relevant Tags
A short introduction about yourself, a profile image, and your Twitter handle (if you have one) so that we can get to know you better and give you credit whenever we share your story. 🤗
How we review and select stories 🤓
The review is simple and straightforward by design. We made it that way to reduce the burden for our contributors yet ensure a high standard for our community. In short, our readers appreciate stories that are:
- Unique and relevant ideas for developers of all kinds
- Well-written in English
- Not promotional
As long as your story follows the above guidelines, it should pass our review.
Additionally, since daily.dev/blog is listed in the exclusive source list of the daily.dev browser extension, we are committed to lead by example and to follow our content guidelines strictly. That means that every single post we publish on our blog must comply with those guidelines as well.
What happens after we approve your story 🥁
Here are some of the benefits of submitting a story to daily.dev:
- We will publish your story on daily.dev official blog and our DEV Publication.
- Your story will be added to the daily.dev browser extension feed (😱). It means that +35K developers from all over the world will have the chance to be exposed to your story every time they open a new tab on their browsers.
- We will share your story on daily.dev’s Twitter, and Facebook.
Additionally, we encourage you to share your story on Twitter, Facebook, and other social media, and be sure to tag @dailydotdev so we can help you promote.
Writer tips and tricks to help you kickstart your writing
There are tons of valuable guides on this topic around the web. However, we wanted to make it easier for you to find the good stuff. We made our collection of tools and articles on how to write stories for developers that can go viral.
Why writing for software developers makes a difference
There are many reasons why we can fill a whole blog post about it. We don’t want to overwhelm you with too much content. We just want to emphasize that writing and publishing content is essential for every software developer’s professional growth.
We’ve gathered some articles that explain this point well, in our opinion.
- The Importance of Writing For Software Developers by Ben McCormick
- The one skill every Software Developer should master by Jens Eickmeyer
- Why developers should know how to write by Derek Mei
Some legal stuff made simple
Your stories stay yours. We will never claim ownership of them. We simply request a right to use and publish them, once reviewed and selected. At any time, you can cross-promote them wherever you want and at your own free will. In fact, we will be more than happy to see you spreading valuable content for as many developers as possible. It is what daily.dev stands for. One last point to note is that there is no option to change the canonical URL for posts published on our blog.
In other words, stories accepted on daily.dev have and will be shared under a non-exclusive license, where content ownership remains with the contributing writer. daily.dev is granted the right to edit, publish, and distribute the story in any of its publishing platforms.
How do I submit a draft?
You definitely reached the right place. Please check the complete guide above. The instruction you are looking for is under the title "How to submit a story."
Do I need to pay to get published? (Hint: definitely no)
Definitely no. We are selecting stories based on their quality and relevance to our developers' community. Paid posts are not welcome since we want to empower our community and provide an equal chance for writers to share their ideas.
We do offer some advertising package, but not in our blog. Suppose you're interested in advertising in daily.dev browser extension, please check the self-serve page.
How long will it take you to review my draft?
We are committed to providing the first feedback within three days from your submission (assuming that you followed the instructions above). However, the process until your article is published might take a bit longer as we will make minor edits and suggest some changes to maximize your story's potential.
Are there things I should be careful about when I write?
If you intend to provide real value to other developers in our community, there's nothing you should be careful about. However, please note that as we genuinely care about the content quality, we will reject a story in the following cases:
- It is not publishing content for developers
- It is for self-promotion only
- It is not in English
- It includes material 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 story you are submitting for review, please refrain from submitting it.
Will you put ads on my posts' pages?
No. We will never place ads on your story’s page in daily.dev/blog.
Can I promote my business or brand on daily.dev?
The daily.dev blog doesn’t allow for paid promotions. We promote content based on its quality and relevance. However, we do offer the option to advertise on our browser extension. If you’re interested in it, please check out the self-serve page