Thread:Sakaros/@comment-26925323-20151023061427/@comment-26925323-20151023073128

Let me step back with you a bit. A coding tutorial works if the user is at the point of needing help with coding. That being said I have learn a few things (mostly the hard way) about user manuals.

 1. Start from the very beginning. Hello! You too can be a part of our Wiki experience!

 2. Explain all your navigation buttons

 3. Do not assume the new user knows how to do anything except type (well, maybe type)

 4. Keep the help pages simple and short…when they get too long break it to a second page or you will lose people

 5. Graphics really help! The csc pages that are referenced somewhere in your wiki are great. I was lucky in that I had two screens at work to use (actually 4, 2 windows and 2 Linux, whatever), so clipping the graphics was easy. It still can be done on one screen, just requires more dexterity.

 6. I always had to write my manuals so that the lowest common denominator in the office could use them…usually that was the boss (only because he did not work operationally often). Meaning, don’t assume people know how to do anything except write a story, or whatever.

 7. If you give them adequate guidance, step-by-step instructions, it might just encourage new submissions from people who would otherwise be intimidated by the nobology.



   I really enjoyed your initial greetings. As I said, it was so nice to get some help.