Become a recognized expert
Share your knowledge and be featured on our Documentation.
Write for the Community program
Join the Scaleway Write for the Community program, an initiative for making our open-source Documentation a truly collaborative knowledge center.
Be rewarded for your contribution
Get up to €200 of cloud credit for each of your publications.
Become a contributor
Before creating your content, carefully read the instructions and conditions below:
-
Read our contribution guidelines, writing guidelines and code of conduct.
-
To be rewarded with Scaleway credits, you must:
- Submit a tutorial idea via a documentation request issue.
- Write the content yourself and submit it following our contribution process.
- Your content must be merged and published by our team.
-
The reward depends on the content length:
- Between 500 and 1000 words: €100 cloud credits.
- More than 1000 words: up to €200 cloud credits.
-
Your contribution voucher is credited directly to your Scaleway account in the month following the publication and is valid for up to three calendar months.
You are now ready to start contributing.
- Clone our public documentation repository on GitHub.
- Create a new documentation request issue to explain your idea. Include a short briefing of what you want to share in the tutorial.
Tip
- Feel free to join our Slack #documentation channel to discuss your ideas directly with the team and our community.
- You can also suggest documentation updates or report bugs by creating a documentation bug issue. Reports are not eligible for a paid reward but are welcomed nonetheless.
- Our team reviews your issue and approves your request. You can then write your content and submit it via a pull request in our repository.
How can I share my idea for a tutorial?
Open a new issue in our GitHub repository using the documentation request template.
Important
Do not forget to include your Organization ID to receive your cloud credits.
You can also create a pull request directly in the docs-content GitHub repository but remember that only content approved via a documentation request issue is eligible for rewards.
How much do I get for writing a tutorial?
If you write a tutorial that gets published on our website, you will receive a voucher of up to €200 cloud credits in your Scaleway account.
Note that for receiving a reward, you must have:
- Submitted your tutorial idea via a documentation request issue, which included your Organization ID and was approved by our team.
- Written the content yourself and followed our contribution process.
- Had your content merged and published by our team.
When will I receive my contribution reward?
Your contribution voucher is credited directly to your Scaleway account in the month following the publication, and is valid for up to three calendar months.
What can I write about?
You can write any tutorial that you think could be useful for Scaleway users. It must involve a Scaleway product and any third-party tools the tutorial involves must be free to use and open-source.
Need some inspiration? Read our existing tutorials to see the kind of content we publish, and try checking our documentation requests or asking for ideas on the Community Slack.
Can I write in a language other than English?
No, all our content is published in English only.
Do I need to complete any additional paperwork after publication?
No, you are all set.
Can I post my content elsewhere?
No. If you submit content to us, this must be uniquely for the Scaleway Documentation website.
What about copyright, do I still own the content?
Scaleway considers any content our own after we publish it and compensate you.
What if I have an idea but do not want to write the content myself?
You are still welcome to get in touch with us.
Submit your idea or suggestion by opening a documentation request or bug issue, and specify that you do not plan on writing the content yourself.
You do not need to include your Organization ID, as you will not be eligible for a reward.
Do you have style guide that I should follow?
Yes! See our guidelines page.