Do you have a story to share that our community or customers would find interesting or helpful? Whether it's about the open source community, software development, collaboration, creation, or something else, we want to hear about it.
Do you love sharing your knowledge? Are you an experienced blogger or technical writer? Are you great at solving challenging problems or explaining complex ideas clearly? We're looking for you!
Have you figured out how to do something awesome with GitLab? Did you conduct an experiment with interesting results? Do you have a specific area of expertise and want to spread the word? We want to publish you.
Pick up an existing issue or create a new one
We need you to create content based on your experience, not the opposite. If you have figured out something amazing to do with GitLab, or from GitLab, and if there's no content on that among GitLab's resources, we would love to publish your tutorial or guide. We're also interested in publishing stories relevant to our open source community or customers. If you experienced something or conducted an experiment and learned something useful from it, that might be a good fit for our blog too.
If you're unsure about how to do what you're willing to write about, we ask you to figure it out first.
Pre-assessment of your writing style
Once you've decided what do you want to write about, add a comment to the issue containing:
A line accepting the terms and conditions:
@rebecca I would like to write about this subject and I accept the
[terms](https://about.gitlab.com/community-writers/terms-and-conditions/)of the Community Writers Program.
Your sample will be pre-evaluated based on your writing style, approach, grammar, structure, context, and flow.
It's time to write your article and send us your first draft
If you passed the pre-assessment stage, you'll see a note in the issue:
@user, you got it! Please write your draft in markdown and send it in a new confidential issue to this project. We do not open any attachments.
Your content must respect our editorial style guide. It must be original and unprecedented. Please do not copy or even loosely paraphrase content from existing articles (from GitLab or anywhere else).
Your first draft will be evaluated
We will review your content in order to improve it
As your content will be published by GitLab, it represents GitLab. Therefore, we will ask you to adjust it according to our quality assurance standards. We may ask you to do a grammar check, content flow and structure adjustments, and improvements specific to your article.
We bet your content will be so awesome that the review will be simple and quick!
Preview your post
Once the review is mostly done, the content team will create a merge request with your post and ask you to review it.
We might ask you for further adjustments, and, once accomplished, it will be merged.
Most contributions to the Community Writers Program will be published on the GitLab blog, but occasionally posts will be better suited to publishing in the GitLab Documentation as a Technical Article. We will let you know beforehand where your content will be published.
Get published, get compensated!
Congratulations! Your article will have been published! We will promote it in social media networks and other channels. Please share with your networks too!
As soon as your article gets published, we will proceed with the compensation process.
If your post is popular, we may invite you to contribute regularly.