Calling all developers who write! We are offering up to $200 per tutorial written. These tutorials will be featured on Semaphore community site and we will credit the author of the content. There is no limit to the number of tutorials you can write.
You can write an article on any tool or topic related to test-driven development, continuous delivery and devops automation. We have a page listing some ideas for writing tutorials which you can use as a starting point.
Our goal at Semaphore is to build a comprehensive and remarkably written collection of articles for software developers. We have bootstrapped Semaphore community with tutorials written by our own engineers, who will continue to actively contribute. But to reach our goal we are going to create an array of community writers who will be paid within a week of completing a new article. We are aiming to document both the basics and the state of the art in the industry, so it is our hope that these tutorials will be clear, technically accurate and of high quality.
How to apply
If you are interested in becoming an official Semaphore community writer, please submit a sample article or blog post and the topics you would like to write about. We will aim to respond to all submissions as soon as possible, but please allow us a couple of days for the initial reply.
When in doubt you should follow the tone and approach of existing tutorials. Grammar and accuracy are most important, so please proofread your tutorial before submitting it.
We are looking for original tutorials to publish on Semaphore community. It is also acceptable to take an existing text, expand it with new information and adapt its format to Semaphore community guidelines.
Let’s do this
Educating developers about leading practices of TDD/BDD, CI, devops and helping them become better software craftsmen is our ultimate goal. The Semaphore community will be the key in accomplishing this objective. If you are interested in taking part in it—and get paid doing it—we are looking forward to hearing from you.