Write for Cloud-Native is a program that supports engineers, technical writers, and community members who are excited to share their experiences and knowledge with the fast-growing cloud-native community. The content will be shared at Magalix's blog with thousands of readers each day.
Through the program, community authors receive a personal payout of up to $200, and can reach an engaged audience of thousands of developers and DevOps engineers directly via their inboxes in the Magalix weekly newsletter, and the Magalix blog.
The work of community authors will grow the cloud-native public knowledge base library of DevOps, software development, and production systems tutorials—all based on free and open-source software.
Check out the Write For Cloud Native articles to get a preview of the community you can join.
The typical payout for content is $100.
Complex production-focused topics may be paid out at up to $200. Updates for existing content, such as distribution changes, are typically paid out at $50 to $100, based on the quantity of changes and technical content.
The number and complexity of cloud-native tools are growing very quickly. The community needs people to help communicate and share something new and apply it everyday.
At Magalix, we were pumped to see the huge community interest in our blog articles. We would like to give the larger community a stage to share their experience and knowledge using great tools, such as Kubernetes, Istio, and more.
We get thousands of unique readers everyday. Our blog is by engineers and for engineers. If you are ready to write about any of the proposed topics, you are ahead of many. Share it with others!
Your articles will teach hundreds of thousands of people all over the globe, and the feedback you receive from Magalix Experts makes the difference between being a good author and a great author.
"I am grateful for the opportunity to write for Magalix. I have written several articles online, but this is the first for which I got the exposure and experience as I did. It challenged me to learn more, and the financial reward was also an encouragement to put in more effort. The editors are straightforward and helpful too. Thank you Magalix."
From start to finish for a new WCN writer, it takes about 2 weeks from outline submission to payment and publication on the blog, per the following process:
Apply: Apply to the program with a writing sample that showcases your ability to explain your technical knowledge to others.
Decide: If you're accepted, you'll work with the editorial team on a topic and outline for your first tutorial. We publish only original, first-run content under a Creative Commons license.
Write: Once your topic is approved, it's time to write. We provide resources, like our writing guidelines, technical best practices recommendations and article templates, to help you get started.
Revise: Submit your first draft and collaborate one-on-one with a professional editor to revise your work.
Publish: After revisions, your editor will send your payment, publish your article, make your charitable contribution—and ask what you want to write about next. Magalix will promote your article across all of our social networks.
Repeat: Build a relationship with the editorial team by suggesting new articles that you want to write.
At a high level, we're looking for these broad categories of content.
Tutorials that walk the reader through creating a real-world project in using any of the cloud-native tools or systems from start to finish.
Use Cases that cover specific problems or scenarios that typical engineers would need to address using the cloud-native tools and systems.
How-To articles that cover advanced systems topics such as Docker, Kubernetes, Ansible, Terraform, and CI/CD
When you apply, we'll send you our public topic list for articles we're actively looking to publish, or you can share your own ideas for unique content our readers will love.
At this time, we're not accepting content about closed-source or paid software, or translations. For copyright reasons, we can't repost content that has already been published elsewhere.