Icon header comm writers

GitLab Community Writers Program

Earn up to US $200 per post published and promoted by GitLab

Issue Tracker Terms & Conditions

What are we looking for?

Creative writers

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.

Comprehensive approach

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!

Rock solid content

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.

What are you waiting for? Join us!

It's your time to get thousands of eyes on your content and earn up to US$ 200 per post!

How does it work?

Your content will be published on the GitLab blog. Occasionally more technical guides will be published as a Technical Article on the GitLab Documentation site.

[ step 01 ]

You choose a subject

Pick up an existing issue or create a new one

We need you to create content based on your experience. 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.


[ step 02 ]

We pre-assess

Pre-assessment of your writing style

Once you've decided what you want to write about, add a comment to the issue containing:

  1. A writing sample (link to content on similar subjects that you published previously)
  2. A brief description of your post. Think about why people would be interested in reading it and why you're the right person to write it.
  3. An introduction for your post
  4. 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.


[ step 03 ]

You draft

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).


[ step 04 ]

We evaluate

Your first draft will be evaluated

Your content will be evaluated by our content team. We will let you know if your post was approved to proceed or not. If approved, you'll receive feedback on your content.

The evaluation is based on particular criteria, defined by the terms and conditions.


[ step 05 ]

We review

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!


[ step 06 ]

We submit a merge request

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.


[ step 07 ]

We publish, you get paid

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.

Take me to the Issue Tracker I want to know the details