We are always looking for technical content writers who would like to earn money on an ongoing basis.
1. Feel the Purpose
Always deliver tested, edited, and valuable technical content that will be useful for developers and system administrators.
2. Understand Our Minimal Expectations
We’re looking for a diverse group of strong technical writers with demonstrated experience in our selected topics. You should have writing experience and be comfortable receiving feedback throughout the publishing process.
Make sure you understand and follow Google’s technical writing guidelines: https://developers.google.com/tech-writing/overview
3. Follow Our Technical Writing Guidelines
All Cherry Servers tutorials are:
- Comprehensive and written for all experience levels
- Technically detailed and correct
- Practical, useful, and self-contained
- Friendly but formal
Comprehensive and written for all experience levels
Our articles are written to be as clear and detailed as possible without making assumptions about the reader’s background knowledge.
We explicitly include every command a reader needs to go from their first SSH connection on a brand-new server to the final, working setup. We also provide readers with all the explanations and background information they need to understand the tutorial. The goal is for our readers to learn the concepts, not just copy and paste code and commands.
We avoid words like “simple,” "straightforward,” "easy,” “simply,” “obviously,” and “just,” as these words do make assumptions about the reader’s knowledge. A reader who hears that something is “easy” may be frustrated when they encounter an issue.
Technically detailed and correct
Our articles are technically accurate and follow industry best-practices. They also provide more details than just the code and commands. We don’t provide large blocks of configuration or program code and ask readers to paste it into their text editor, trusting us that it works. We provide all the details necessary for the readers to understand it.
Every command should have a detailed explanation, including options and flags as necessary. Every block of code should describe what it does and why it works that way. When you ask the reader to execute a command or modify a configuration file, first explain what it does and why you’re asking the reader to make those changes. These details give readers the background they need to grow their skills.
Practical, useful, and self-contained
Once a reader has finished a Cherry Servers article, they should have installed, built, or set up something from start to finish. We emphasize a practical approach: at the end of an article, the reader should have a usable environment or an example to build upon. Our articles cover the topic thoroughly and provide more value than one can find at competing content creators.
Authors should link to existing Cherry Servers articles, if able, to set up prerequisites that readers should follow before beginning the tutorial, and link to available Cherry Servers articles to provide additional information in the body of the tutorial. Authors should only send readers offsite to gather information if there’s no existing Cherry Servers article and the information can’t be added to the article directly in a short summary. Completely avoid sending readers to articles created by competing cloud infrastructure providers.
Friendly but formal
Our tutorials aim for a friendly but formal tone. This means that articles do not include jargon, memes, excessive slang, emoji, or jokes. As we’re writing for a global audience, we aim for a tone that works across language and cultural boundaries.
We are supportive and encourage motivational language focused on outcomes. For example, instead of "You will learn how to install Apache”, try “In this tutorial you will install Apache”. This motivates the reader and focuses on the goal they need to accomplish.
4. Choose Your Content Type
Users reading your articles are primarily interested in server administration and application development. Therefore, our documentation library consists of these major categories:
- How-to Guide is an educational article with detailed step-by-step instructions on how to build stuff written for developers and system engineers. This content should result in having a working proof of concept. It may be an installation guide, a quick-start guide, a best practice guide or similar pieces of content.
- Informational Articles is a general-purpose text about a technological topic that lacks code examples. It may be an article that tries to explain some technical concept or system architecture.
5. Pick a topic
You may write How-to Guides and informational articles for the following topics:
- Linux
- Docker
- Ansible
- Terraform
- Kubernetes
- PostgreSQL
- Servers (load balancing, dns, vpn, minecraft, etc.)
We generate an article wish list with specific article subjects for these topics for you to choose from. You may also suggest your own articles to be added to the wish list. Our wish list may include topics like:
- Topic (Linux), Content Type (How-to Guide), Subject (How to Manage Linux System Routing Rules With iptables?)
- Topic (Docker), Content Type (Info Article), Subject (A Complete Overview of Docker Architecture)
- Topic (PostgreSQL), Content Type (How-to Guide), Subject (How to Use PostgreSQL Stored Procedures?)
6. Write Well, Earn Handsome
We are only paying for high quality content that meets these Content Writing Guidelines. If we decide that your article is of poor quality, low value, and requires a significant amount of editing, we will reject your article and do not compensate you for it.
How-to Guide Pricelist:
- Up to 750 words, excluding code – $150
- Up to 1500 words, excluding code - $300
- More than 1500 words, excluding code - $450
Informational Article Pricelist:
- Up to 750 words - $100
- Up to 1500 words – 200$
- More than 1500 words - $300
If you would like to write an article for Cherry Servers and start earning money, please drop a line to mantas.levinas@cherryservers.com