- If someone has just ordered a new server, they should not have to install or configure anything first, except it is explained in your tutorial. In that case, make sure there is already a tutorial that explains it and link to it at the beginning of your tutorial.
- Don´t skip steps. Some might seem obvious or self-explanatory to you, but aren't to others.
- Don´t overdo insider jokes. (Looking over to you, dear "Duck-Community". :wink:)
- Be the original.
- We will not accept tutorials that can be found anywhere else on the web, especially if not in context with netcup.
- Make sure your tutorial is new to the collection. In case it's not, have a look if it would be a valid expansion of an existing tutorial. In case you found one, don't hesitate to reach out to us.
- After you create a pull request, don't keep editing your tutorial unless we specifically ask you to do so. Otherwise, the review process will take longer than necessary. If you forgot something, either we or the community will notice it and ask you to add the missing information.
- Submit one tutorial at a time.
- To keep our review structured and efficient, you should only submit tutorials that contain one instruction at a time. Don't squeeze several tutorials into one file. You can always submit several separate tutorials.
I have read and understood the Contributor's Certificate of Origin at the end of the [template](https://github.com/netcup-community/community-tutorials/blob/main/TEMPLATE.md) and I hereby certify that I meet the contribution criteria described in it.
If your tutorial is accepted, you will receive an email from our netcup Community Team asking for your netcup Customer-ID, so the reward can be processed.
The title should be a summary that gives users an immediate idea of what the tutorial is about. e.g. Installing <software> on <OperatingSystem>
## Introduction
The first few sentences are here for you to explain what your tutorial is about. Make sure to be on point with what users will end up with when they finished your tutorial. Also: let them know if there are special requirements! Link other tutorials that your tutorial builds on, and add recommendations for what users should know.
## Steps
Now we're right in the heart of the tutorial where users will follow every single one of your (foot)steps.
The amount of steps will vary depending on how long or complicated your tutorial is.
Remember: none of the users walked that road before, so make sure to really explain your steps well.
Each of them should build on the previous one. It is important not to skip any steps, no matter how obvious or self-explanatory they may seem! (If you're not sure what we mean here, you might want to watch this fun video: https://www.youtube.com/watch?v=cDA3_5982h8&t=4s)