From: "Peter Neilson" <neilson@windstream.net>
To: emacs-orgmode@gnu.org
Subject: Re: Org Tutorials need more structure
Date: Mon, 30 Sep 2013 14:36:35 -0400 [thread overview]
Message-ID: <op.w38ly9nwrns8nc@localhost.localdomain> (raw)
In-Reply-To: <8761tiuttm.fsf@ucl.ac.uk>
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!
next prev parent reply other threads:[~2013-09-30 18:36 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-28 6:11 Org Tutorials need more structure Carsten Dominik
2013-09-28 7:22 ` Joseph Vidal-Rosset
2013-09-28 8:37 ` Marcin Borkowski
2013-09-28 10:30 ` Suvayu Ali
2013-09-28 11:59 ` Joseph Vidal-Rosset
2013-09-28 12:36 ` Eric Schulte
2013-09-28 13:10 ` Joseph Vidal-Rosset
2013-09-28 16:02 ` Suvayu Ali
2013-09-28 17:19 ` Joseph Vidal-Rosset
2013-10-01 7:59 ` Eric S Fraga
2013-10-01 20:34 ` David Rogers
2013-10-01 21:00 ` Marcin Borkowski
2013-09-28 8:48 ` Marcin Borkowski
2013-09-28 10:09 ` Carsten Dominik
2013-09-28 14:26 ` Charles Millar
2013-09-28 16:35 ` Carsten Dominik
2013-09-28 17:14 ` Ian Barton
2013-09-28 17:43 ` Marcin Borkowski
2013-09-28 17:48 ` Carsten Dominik
2013-09-28 19:06 ` Ramon Diaz-Uriarte
2013-09-28 19:52 ` Thomas S. Dye
2013-09-28 20:50 ` Charles Millar
2013-09-28 21:31 ` Marcin Borkowski
2013-09-28 21:52 ` John Hendy
2013-09-28 23:14 ` Charles Millar
2013-09-28 23:29 ` Thomas S. Dye
2013-09-29 0:29 ` John Hendy
2013-09-29 7:28 ` Suvayu Ali
2013-09-30 8:04 ` Alan Schmitt
2013-09-30 17:01 ` Eric S Fraga
2013-09-30 18:36 ` Peter Neilson [this message]
2013-09-30 21:07 ` Eduardo Ochs
2013-10-01 8:52 ` Michael Brand
2013-10-01 5:34 ` Suvayu Ali
2013-10-01 8:55 ` Marcin Borkowski
2013-10-01 12:40 ` Joseph Vidal-Rosset
2013-09-30 17:56 ` Thomas S. Dye
2013-09-29 8:44 ` Eric Abrahamsen
2013-09-29 15:31 ` Matt Price
2013-09-30 7:25 ` Eric Abrahamsen
2013-10-01 14:08 ` William Denton
2013-10-02 1:10 ` M
2013-10-02 18:06 ` Alan E. Davis
-- strict thread matches above, loose matches on Subject: below --
2013-09-29 16:43 Rustom Mody
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=op.w38ly9nwrns8nc@localhost.localdomain \
--to=neilson@windstream.net \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).