I think you should consider rewriting the Hugo Manual.
I am not the author of the Hugo Manual, so I could not re-write it, per se. What I was doing here was trying to provide a bit of a supplement to the manual. Often what I do when learning anything is then write down my thoughts and try to present those in a way that I wish had been available when I was learning. Note that in the tutorial there are often times where I do suggest the reader go to the manual to check up on things further. But I also indicate where I differ from the manual, which is only in the case of terminology on a few small points.
Were I you, I'd get rid of the idea of a tutorial and literally start making a sort of 'Hugo Book' or something because I think the tutorial approach is forcing you to avoid some subjects or treat them lightly.
Yes, that is sort of true in terms of avoiding some subjects. This mainly happens because you figure, when writing, "Oh, yeah, I guess I should explain
that, too. But it does not fit here. Hmm. Guess I will have to figure out how to throw that in." And then 'throwing that in' makes your tutorial start to get a little disjointed. So maybe what we need to do is come up with a sort of "Hugo Beginner's Guide" - one that graduates from easy material to more advanced material.
I'd probably drop the media elements except as maybe a 'supplement' to the main text.
I know that the media elements seem sort of tacked on, so I understand what you are saying here. I still would like to include them in some fashion (and not just as supplement) because many of the Hugo games out there (particularly games like
Guilty Bastards,
Fallacy of Dawn and
Necrotic Drift) tend to use a lot of graphics and sounds. But, maybe, with the idea of a "Programmer's Guide" the media portions could fit into the later, more 'advanced' sections.
Thank you for the comments as this has given me some things to think about.