From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: Org Tutorials need more structure
Date: Mon, 30 Sep 2013 14:25:06 +0700 [thread overview]
Message-ID: <877gdyu5yl.fsf@ericabrahamsen.net> (raw)
In-Reply-To: CAN_Dec9dDqEW8o8Oc7wZo02AEXK1=vGED61_nNQTtF5=yn94Sw@mail.gmail.com
Matt Price <moptop99@gmail.com> writes:
> On Sun, Sep 29, 2013 at 4:44 AM, Eric Abrahamsen
> <eric@ericabrahamsen.net> wrote:
>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>>
>>> Hi everyone,
>>>
>>> today I looked at our tutorial page at
>>>
>>> http://orgmode.org/worg/org-tutorials/index.html
>>>
>>> and came away with the feeling that that this page has become
>>> somewhat useless for people who are really new to Org. I think
>>> the page should start with a section of true recommendations
>>> for beginners, a path we tell every new users to take in order to
>>> learn about Org mode.
>>>
>>> Can we have a discussion here on how this path should look like?
>>> When you came to Org-mode as a newby, what were the three resources
>>> that really made an impression on by being accessible and
>>> providing feel and promise for digging deeper?
>>>
>>> - Carsten
>>
>> My feeling is, the tutorial structure might look like this:
>>
>> Start with the basics: outlining and structure editing, plus
>> introductions to links and properties.
>>
>> Then four other tutorials, presented in no particular order:
>>
>> 1. TODOs/agendas/task management (plus clocking)
>> 2. Exporting
>> 3. Babel
>> 4. Tables/spreadsheets
>
> I would only add that "exporting" is closely linked to "writing in
> org" whcih is what I mostly do. This includes topics like footnotes,
> which I haven't really figured out yet after 3 years of using org
> (admittedly I haven't really tried either).
Right, but I think my point was that you can learn pretty much
everything there is to learn about authoring and note-taking in org
(including footnotes and lists and all that good stuff), without even
being aware that the export engine exists. So that can be a completely
self-contained tutorial.
Then one day someone tells you about exporting. You export your document
into six different formats, and your jaw drops. You instantly want to
start tweaking the output, and then (and only then) you read the
tutorial on exporting, which introduces you to backends, export options,
bits of literal backend code, and filters. This tutorial doesn't even
need to touch on issues of content or structure, because you've already
read about that in tutorial one, and this is /only/ about making your
documents appear differently in different output formats.
> It might also be nice if these tutorials included some sample setup
> code to get intermediate-to-advanced features working even before one
> fully understands them.
I fully agree in theory, but when you start thinking about the
complexity of custom agenda commands, or babel header lines, or TBLFM
lines... that's pretty brutal stuff.
next prev parent reply other threads:[~2013-09-30 7:24 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
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 [this message]
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=877gdyu5yl.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.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).