GoldenDuckFloats
New Member
I need some help making a tutorial that gradually builds up a reader's technical sophistication (Particularly on how to install and manage software). By providing a roadmap of what new users should know and present them in an order that makes sense.
Each subject can have a short yet detailed description and instead of writing step-by-step instructions ourselves, we reference online web-pages that people have already written. There are plenty of threads on here about system-diagnostics and various programs, but hardly anything that ties them together. We can also look for any gaps that need to be filled in and add them to the description.
One of the reasons why there aren't many Linux users is partly due to how the more experienced users keep telling newcomers to just read the man pages. This is terrible advice, considering there are so many commands that obscure the ones we should be using. Sometimes a simple description of a command and its options isn't enough. We need examples of the different situations it can be applied in and an explanation for the technical jargon that Man-pages don't bother to explain.
Also, it would be more effective to arrange subjects based on 'when' beginners will need to know about them. Such as needing to know how to navigate the Command-Line with cd before teaching the ls command. This should hold true for more complex topics, such as managing servers.
For collaboration, we can either:
Each subject can have a short yet detailed description and instead of writing step-by-step instructions ourselves, we reference online web-pages that people have already written. There are plenty of threads on here about system-diagnostics and various programs, but hardly anything that ties them together. We can also look for any gaps that need to be filled in and add them to the description.
One of the reasons why there aren't many Linux users is partly due to how the more experienced users keep telling newcomers to just read the man pages. This is terrible advice, considering there are so many commands that obscure the ones we should be using. Sometimes a simple description of a command and its options isn't enough. We need examples of the different situations it can be applied in and an explanation for the technical jargon that Man-pages don't bother to explain.
Also, it would be more effective to arrange subjects based on 'when' beginners will need to know about them. Such as needing to know how to navigate the Command-Line with cd before teaching the ls command. This should hold true for more complex topics, such as managing servers.
For collaboration, we can either:
- Write paragraphs in the thread as a quote.
- Upload a .pdf or document file to GoogleDrive or an equivalent file-sharing service and share a link so others can fork your work.
- Share the .pdf file in the thread or open a .pdf in your browser as a new tab and take a screen-shot and post that in the thread instead.
Last edited: