Frequently Asked Questions 🤔
Some of these are not actually asked frequently, but they're still good to know.
Anyone! Yes, you have permission to make a new post of any kind as long as it meets our community guidelines and gets through common-sense spam filters. Your post is subject to removal at the discretion of the moderators if they believe it does not meet the requirements of our code of conduct.
Click on "Write a Post" in the top right corner of the site. Write your article, give it a title, tag it with appropriate tags, and fill out any other relevant fields. Then, once you're ready, change
published: false to
published: true in the front matter of the post and save. Your post will now be published.
The home page is selected by our editorial team. You can email us with any specific questions.
Absolutely, as long as you have the rights you need to do so! And if it's of high quality, we'll feature it.
You can add or remove Twitter/GitHub associations from your settings, but note that you can only do this if both Twitter and GitHub are connected to your account. If you have any issues with this, email email@example.com and we'll take care of it.
You can set the canonical_url of your post before publishing so that Google knows where to send the link juice (that precious, precious link juice).
In your post editor, click the menu button:
Then fill in your canonical URL!
If you're using the basic markdown editor, you can add it inside the triple dashes, like so:
--- title: published: false tags: canonical_url: https://mycoolsite.com/my-post ---
Please create an issue on our repo.
Please email firstname.lastname@example.org.
For a specific comment: navigate to the comment and click the dropdown arrow to report abuse.
For a specific article: navigate to the article, scroll to the bottom and click report abuse.
In general, you can fill out the report abuse form.
If you have questions about sponsorships (i.e. how to turn off sponsor displays), visit our sponsorship info page.
You'll find the option to delete your account in your settings. Self-deletion will remove your DEV profile, and all articles, comments, Connect messages, etc.
If you require a full GDPR deletion, please e-mail email@example.com with the subject line "GDPR Delete Request" and we will ensure that any of your remaining data is purged from all systems.
Yes, you own the rights to the content you create and post on dev.to and you have the full authority to post, edit, and remove your content as you see fit.
By posting content on dev.to, you give us a nonexclusive license to publish it, including anything reasonably related to publishing it (like storing, displaying, reformatting, and distributing it).
No ad will ever be placed next to a user's post without their consent in the matter.
cover_image: [url] in the front matter of your post. For more information on our editor, check out our editor guide.
Comments are threaded with a maximum depth, and then they become flat. You can respond to flattened-out threads by replying to the last comment in the overall thread.
Yes. To hide a comment that was added to one of your posts, simply click the dropdown connected to the comment and select the "Hide" option. You can read our original changelog post on the feature for more information.
We don’t disallow profanity in general, but we do have an internal policy of not boosting posts through our social channels that have profanity in the title, so you might want to keep that in mind.
Yes, you can. The link for our main feed can be found here: https://dev.to/feed. For user-specific feeds, you can find them via
https://dev.to/feed/username. For tag-specific feeds, you can find them via
Upon sign in, why do you require authorization to allow the DEV Community to access info on my Twitter account?
The authorization page being talked about looks like the following:
This is the default scope for Twitter and to our knowledge we can't get any more granular than this. Here's a picture of our options and what we've chosen:
We take a strong stance against collecting unnecessary data on our users as stated on our privacy page.