- Tutorials must adhere to the forum Code of Conduct.
This should go without saying, but any tutorial which is condescending or otherwise contravenes forum policy will be removed.
- Tutorials should be written to the level of a complete Linux newcomer.
Please do not assume that your reader understands how to compile source code, or which dependencies are necessary to get started. Make sure you mention all the steps required to finish the tutorial, and don't assume your reader will have information you omitted.
- Tutorials should be easy to read and follow.
A good tutorial is educational and visually appealing. Include proper code boxes, highlighted instructions and clean spacing, along with screenshots if possible. Tutorials that are difficult to follow, haphazard or unformatted will be removed.
- Tutorials should be written in clear and proper English.
In a situation where you are giving instructions to another user, it is important to be as clear as possible. If a tutorial is difficult to understand, or uses broken English or slang (that includes leet, or anything that resembles it), it will be removed.
- Tutorials should be complete, from start to finish.
A tutorial that closes with "I'll post more on that later" will be removed, as will tutorials that suggest reading other pages to complete a task.
- Tutorials should cite sources, and link to offsite sources if possible.
If you are borrowing an idea or a procedure from another source, you should give credit to that author and link to their explanation. This is not only polite, but it also gives the reader the chance to get more information or help.
- Tutorials may not be copy-and-pasted from outside sources.
Copying a wiki page or a tutorial from another forum and pasting it here is plagiarism, and is a violation of the forum Code of Conduct. If your tutorial has been stolen from another source and you do not offer credit to the original author or meet the author's licensing requirements, it will be deleted.
- Tutorials should explain how they were tested, and under what conditions.
It is impossible for forum members to judge the technical merit of your tutorial. For that reason, you should include as much information as possible on how your tutorial was tested -- that includes hardware and software, as well as the release edition or any other technical points you can offer.
- Tutorials should explain how to revert changes.
Your explanation should include a process for reversing the changes, uninstalling the software or otherwise restoring the original condition of a system. This is an added precaution in the case that your method doesn't succeed, and a reader is left with an incomplete system or broken package.
- Tutorials should be supported.
You are expected to offer support for your tutorial, within practical limits. If you fail to respond to requests for help or clarification within a reasonable time, or fail to update your tutorial, the thread will be closed or removed.
- Malicious content
Posting something that contains malicious content or content that could lead to system damage will result in a ban.