Guidelines to submit your content in ProstDev
Please take care of the following guidelines before submitting your application to contribute.
Thank you for your interest in creating a post with us! We’ve been getting more articles lately but our bandwidth to review them is a bit decreased at the moment. Because of this, the time we spend reviewing the posts will need to be reduced.
We want to keep serving our readers with great quality content, so our quality standards will have to be enforced by you before sending your application. Once you’ve followed the guidelines, we can start the review process.
Your application might be delayed or rejected if your contribution does not comply with the standards.
- Your article needs to be created in Google Docs before submitting.
- Please make sure your document has the appropriate editing access for us to make editions to your file.
- The title of your article must be 100 characters or less.
- The contents of your article must be between 500 and 1,500 words. Note that specific content within the article (like tables or code blocks) might make the article longer than it is. If this is the case, please let us know when you submit your application or create gist files for the code (next point).
- Any code blocks with more than 5 lines of code must be replaced with public gist files. Please read this Article Formatting section for more information.
- If you copy/paste quotes, pictures, or code from other sites, you need to provide the link where you got it from. We don’t accept any form of plagiarism.
- We will reject content that has not been proofread before submission. To proofread your content, you can use services or systems that check your grammar, like Grammarly or Hemingway; or ask a friend to review your content first.
- Once you’ve taken care of all these, you can submit your content here. Please note that you will need a GitHub Account.
Once you submit your content, we might take between 1-2 weeks to get back to you, depending on our current content queue. Any missed guideline/standard from the previous list will result in rejection or further delays in your review process.
If your content is reviewed on time and follows the appropriate standards, we can publish your content as soon as 2 weeks. If further editions are required from your side, the publishing date will be extended. Any round of editions might add an additional week to the publishing date depending on our queue. Please be patient.
Thank you!
FAQs
Frequently asked questions about this post.
-
How long should my article be to be accepted?
The contents of your article must be between 500 and 1,500 words. If specific content like tables or code blocks pushes it longer than that, let us know when you submit your application or create gist files for the code.
-
What's the maximum length for the article title?
The title of your article must be 100 characters or less.
-
Where do I write and submit my article?
Your article needs to be created in Google Docs before submitting, with the appropriate editing access so we can make edits to your file, and then you submit your content at https://github.com/ProstDev/blog-posts/issues/new/choose , which requires a GitHub account.
-
How do I handle code blocks longer than 5 lines?
Any code blocks with more than 5 lines of code must be replaced with public gist files; see the GitHub gists guide at https://docs.github.com/en/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists and the Article Formatting section at https://www.prostdev.com/post/prostdev-s-new-blog-post-template#viewer-eg9k8 for more information.
-
How long does the review and publishing process take?
After you submit, we might take between 1-2 weeks to get back to you depending on the current content queue, and if your content is on time and follows the standards we can publish as soon as 2 weeks; if further editions are required from your side, each round might add an additional week to the publishing date.
-
Why might my submission be delayed or rejected?
Your application might be delayed or rejected if your contribution does not comply with the standards, including any form of plagiarism, content that has not been proofread, or any missed guideline from the submission list. To proofread you can use tools like Grammarly at https://grammarly.com/ or Hemingway at https://hemingwayapp.com/ , or ask a friend to review first, and any quotes, pictures, or code copied from other sites must include the link where you got it from.