Vultr Docs is our knowledge base for the Vultr community. You've come to the right place if you are a technical writer looking for assignments. This article covers our rules, payments, and frequently asked questions. After you've familiarized yourself with the program, a review of the following resources is required before getting started:
Articles related to the following shall not be accepted:
Article due dates provide a structured timeline for the author as well as the Vultr Docs Team. All articles must be submitted for review within four weeks of accepting the assignment. We do not send reminders or status requests; it is your responsibility to contact us with questions about the assignment deadline. If the Vultr Docs team has not received your article by its due date, we will consider the assignment incomplete and re-post it on the assignment dashboard for another author.
These payment rates are guidelines; each article is evaluated individually. Payments are based on the amount of original writing, excluding code blocks. The Vultr Style Guide must be used for all assignments.
If the Vultr Docs Team discovers technical errors or needs to edit your article, the article is not eligible for full payment, so carefully proofread and test your work before submitting it to us.
New articles that are ready to publish without editing by Vultr are eligible for the highest payments and an author's byline.
Vultr Docs pays 50% of the new article rate, up to a maximum of $300, for ports of existing articles. Ports are guides rewritten for different platforms, such as an Ubuntu installation guide adapted to support FreeBSD. Ports should contain important new information and should not plagiarize the original article. Ports with only minor differences are not eligible.
Vultr Docs pays 50% of the new article rate for updates based on the amount of new content. Updates should contain significant new information and should not plagiarize the original article. Updates with only minor differences are not eligible.
Users reading your articles are primarily interested in server administration and applications. Therefore, our documentation library consists of these major categories:
Ensure an assignment has been approved before you begin writing. There may be suggestions, questions, or updates to the assignment notes. We will notify you when your assignment is ready.
Our article submission system does not allow directly embedding images in Markdown for security. If your article includes images, please upload it to a public location such as imgur.com, and then use a standard Markdown image directive like this:
![Alt text for image](https://i.imgur.com/example-filename.png)
Important note about images: Articles in Vultr's documentation library must be accessible, which means all images need alternative descriptive text. As a general rule, use images sparingly unless required. If you use images, include sufficient information so a person who cannot see the image can use your article.
You can be anonymous instead of publishing your name on your articles.
Vultr does not publish aliases for author credit. You can leave the author's name blank if you prefer not to use your real name.
You do not have to pay to write for Vultr Docs, but we need a linked payment method to verify your account. When you connect your credit card, you can choose "I just want to link my credit card - $0.00 deposit," and you will not be charged. However, you must test your article's steps to produce quality documentation. This usually means you need to deploy a small cloud server for a few hours, typically costing less than $1 — a small critical investment in your article that pays up to $600 when published. If you cannot afford to deploy a Vultr cloud server, you could test locally in QEMU or VirtualBox, but most authors see the value in testing on our infrastructure.
Yes, Vultr has an available assignment list.
Before you submit your article, please request an assignment:
To avoid assignment conflicts, we assign one article at a time. Creating multiple accounts to circumvent this policy is prohibited and violates Vultr's Terms of Service.
Some authors rush to deliver multiple articles to maximize their income. Unfortunately, these articles are usually low quality and require our team to edit them, resulting in lower payments if published. However, you can increase your payments by following a few tips:
Requesting an article assignment or accepting an assignment does not create any obligation by Vultr to publish your article. We may ask you to make changes or corrections, or the team may decline to publish your article without an explanation. We will make a payment offer after reviewing your article.
We do not provide reviewer notes if we choose not to publish your article.
Not every article will be accepted for publication even if it meets all program guidelines. The decision to publish an article depends on many business factors, and Vultr reserves the right to decline to publish articles without a detailed explanation.
Our approval of an outline concept does not create a contractual obligation to publish an article. It only means the outline isn't on our list of unpermitted topics.
Payment for articles does not constitute an employer-employee relationship. Therefore, authors may not represent themselves as Vultr employees online.
These payment rates are guidelines; we evaluate each article individually, prepare a payment proposal, and obtain your consent before publishing. We will not publish your article unless you agree with our proposed payment.
Unfortunately, no. Please keep a copy of your article before submitting it. How did you test and edit the article if you don't have a saved copy?
We do not pay in Bitcoin or Payoneer. You may choose to receive payments through PayPal or Vultr account credit.
You are welcome to use a different PayPal address than your Vultr email address.
Yes, if the article is specific to Vultr Bare Metal. Vultr cloud servers do not support nested virtualization.
No, you must include all code samples in your article. However, at our discretion, we may choose to migrate your code samples to the Vultr Docs GitHub repository.
After you submit your article, our team will review it. The review time varies; we publish a current estimate on the assignment dashboard. If your article is approved and you accept our payment proposal, the payment team typically makes the payment within five business days.
MDTK is helpful, but it is not a substitute for a human. Most articles will have MDTK warnings that don't need corrections. Please send us suggestions and comments on issues you find. Make sure to download the latest version of MDTK from GitHub because we update it frequently.
Thank you for contributing to Vultr Docs! Please use the "Suggest an update" button below each Vultr Doc to report errors in our documentation. Also, if you have questions about the Vultr Docs program, do not hesitate to contact us. We appreciate your feedback.