"Learning the basics of Leo would be the obvious first step."

Exactly my point. What is perfectly obvious to you was not perfectly
obvious to me. At which point I am either a dolt or offended and moving on
to something else.

Hence my recommendation to explicitly state the prerequisites for the
tutorial or to make it very clear where it fits into the hierarchy of
tutorials/documentation.

People will willingly give up rather than appear stupid, especially to
themselves.

Chris


On Sat, Nov 2, 2013 at 10:26 AM, <[email protected]> wrote:

> On Saturday, 2 November 2013 16:11:00 UTC+1, Chris George wrote:
>>
>> Not to be too picky, but I found this confusing. Is there a prior
>> tutorial that covers some of this (things like @settings trees within
>> documents) that should be completed before the rst3 tutorial? What is the
>> required knowledge level of your target audience for this tutorial?
>>
>> Are you assuming a person with little or no knowledge about Leo going
>> through this tutorial or are there prerequisites? If there are
>> prerequisites, would it not make sense to detail them at the beginning?
>> Something like "Someone going through this tutorial should have a basic
>> idea about (concept x) and have completed (tutorial Q). What is blindingly
>> obvious to you may not be so obvious to someone else. If the rst3 tutorial
>> is part of a hierarchy of concepts, where does it fit? Another
>> example: Does the rst3_call_docutils setting go in the node or the body? If
>> I have zero experience with the @settings tree in a .leo document (only
>> having met the idea in relation to the two settings files), this becomes a
>> question in my mind.
>>
>
> I could hardly resist the temptation to chime in on this cue. I hope that
> no one minds hwat I am going to say, but I experienced exactly the same
> problem (with the general Leo documentation). Granted, you guys are doing a
> terrific job with the documentation, but there are still some blind spots
> to cover. What I mean is that, from my experience, the documentation is not
> basic enough for the total newbie. I started reading the documentation a
> couple of months ago, with great enthusiasm, but dropped out after a short
> while, simply because I was not able to understand the concepts being
> cross-referred to. I felt as if the documentation somehow assumed that the
> reader has some prior knowledge, which I did not have.
> Now that in the the last couple of months there has been a flurry of
> activity (especially on Edward's part) for improving the documentation, for
> which we are thankful (I, for one), I think I will try again.
> Please, make sure that every new concept introduced is properly
> explained.
>
>  --
> You received this message because you are subscribed to the Google Groups
> "leo-editor" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/leo-editor.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to