Did you search GitLab resources for a guide or a tutorial and didn't find it? Would you love to see us expanding our range of guides and tutorials and advice about creating, collaborating, and deploying with Git and GitLab? We need your help.
Are you keen to make your content comprehensive to everyone else? Do you love teaching others? Do you have experience writing technical content? Are you an experienced blogger? We are looking for you.
Have you figured out how do to an awesome thing with GitLab and would be delighted to share your knowledge? Are you great at solving challenging problems or explaining complex ideas? Do you have a specific area of expertise and want to spread the world? 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.
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:
@marcia I would like to write about this subject and I accept the terms 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
Considering that 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 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!
Submit a Merge Request
The technical writing team might ask you for further adjustments, and, once accomplished, it will be merged.
Get published, get compensated!
Congratulations! Your article will have been published! We will promote it in social media networks and other channels.
As soon as your article gets published, we will proceed with the compensation process.
If you succeed on the first process, we'll invite you to write for us regularly.