Re: Org Tutorials need more structure

["Peter Neilson" <neilson@windstream.net>]

On Mon, 30 Sep 2013 13:01:57 -0400, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

> but I'm sure somebody else will think something is missing

I'll admit that I've only dabbled in org mode thus far, but here's what I  
see as lacking in the tutorial documentation:

1. Non-video presentations for beginners. Some of us are (for one reason  
or another) badly set up to use video. Perhaps our network connection is  
slow, or our system is flaky and crashes with video. Or perhaps we only  
have five or ten minutes at a time to study. Or perhaps we are mostly  
trying to learn from hard copy we've printed out. A few of us might even  
be blind.

2. Goal-oriented presentations. Instead of telling us, "The XX widget  
allows you to do the YY operation," we might be hoping to see, "To  
accomplish ZZ (for instance, task scheduling), do something like this:  
(neat example with pointers to syntax)"

The user will hope to see examples, even annotated examples. Sometimes  
negative examples: "DON'T try it this way... It seems right, and it's  
alluring, but ultimately it won't work, and you'll never figure out what's  
wrong."

There ought to be discussions of why we should think of the problem THIS  
WAY and not THAT WAY.

It may be that there are portions of the existing docs that cover  
everything I see as deficient, and I've just not found them. Perhaps a  
pointer to LOOK HERE FIRST is needed for those docs.

I'll end with a quotation from a leader in a club to which I once  
belonged: "Yes, I can see how you might think that's a problem. How would  
you like to CHAIR THE COMMITTEE to solve that for next year's convention?"

Perhaps I'm volunteering!