What Do We Write About?
Our library covers a broad range of open-source cloud computing technologies with a focus on free software. This includes but is not limited to:
We are currently accepting freelance applications for any of these subjects and documentation formats, but with a higher priority on Kubernetes, Linux essentials, and databases.
Documentation takes on a few different forms
Meet the technical writing team
Why Write For Us?
Linode’s library is a long-running and popular resource for developers, engineers, and others.
By contributing, your work will be a part of this well-established, trusted reference.
Get paid for your work
You will be paid a minimum of $300 for original guides. Updates to existing guides start at $100 each.
Work with modern documentation processes
Linode's library is hosted on GitHub, and by contributing to the library, you'll be adding to your portfolio on GitHub. Our library is also maintained under the docs-as-code methodology, where the tools you use to write documentation are the same tools used to write software. As a contributor, you'll be:
- authoring your drafts in Markdown;
- previewing your drafts with Hugo, our static site generator;
- version controlling your work with Git; and
- reviewing Linode's automatic unit tests of your drafts, which will check for spelling, styling, and other issues.
Note: If you’re not familiar with one or more of these tools, we’ll provide resources to help you adopt them.
Because docs-as-code is becoming more popular, the skills you’ll exercise when writing for Linode are transferable to other work. In particular, documentation is a valuable asset for open-source projects (as evidenced by programs like Google’s Season of Docs), and we hope that Write For Linode authors are well-prepared to contribute to open-source projects too.
How To Get Started
If you’re interested in becoming a contributor, you can get started by completing our application form, which is an opportunity to highlight your existing writing portfolio. We are currently prioritizing contributions related to Kubernetes, Linux essentials, and databases.
Next steps after applying
If your application is accepted, you’ll work through our three-step editorial workflow to write and publish your first guide or tutorial:
First, you'll collaborate with our team to identify a topic to write about—either an idea that you submit, or one that we suggest. Then, you'll start writing. To make sure you're set up for success, the technical writing team will take special care to define clear expectations for your first draft. We will deliver to you:
- The Linode Writer's Guide, which provides a laundry list of all of the formatting features available in our publishing system and sets forth all style requirements.
- A set of sample phrases and messaging that you can insert into your guides.
- A contributor's rubric that we will later use to review your guide draft. This rubric helps us make sure that all new documentation conforms to the style conventions of our library.
- Instructions for how to submit your work to our repository on GitHub.
Once you submit your draft, the next step is our review of your contribution. We'll request changes where appropriate (including our reasoning behind those requests). You'll team-up with a dedicated editor to refine the draft until it's ready for publication.
When your guide is ready, the last step is publishing it to our library, which we handle. Payment for your guide will be sent to you. The new guide will be advertised on Linode's social media accounts and elsewhere.
If you've finished your first guide and would like to write another, there's no need to re-apply—just reach out to your editor and let them know that you have more guide ideas.
The quality of your writing sample is the primary way we evaluate your application to become a freelance contributor. Please submit one or more examples of technical documentation you’ve written in the past that demonstrate your expertise on Linux or a cloud-related topic.
Fields marked with * are required.
The form is loading
Please reload the page and try again.