From: Carsten Dominik <carsten.dominik@gmail.com>
To: Marcin Borkowski <mbork@wmi.amu.edu.pl>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org Tutorials need more structure
Date: Sat, 28 Sep 2013 12:09:09 +0200 [thread overview]
Message-ID: <68CAD3FD-52FD-4D7D-A4BA-E4823F57E506@gmail.com> (raw)
In-Reply-To: <20130928104846.52fbe04c@aga-netbook>
[-- Attachment #1: Type: text/plain, Size: 3353 bytes --]
On 28.9.2013, at 10:48, Marcin Borkowski <mbork@wmi.amu.edu.pl> wrote:
> Dnia 2013-09-28, o godz. 08:11:23
> Carsten Dominik <carsten.dominik@gmail.com> napisał(a):
>
>> 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?
>
> As I hinted in my previous email, there are two cases:
>
> 1. Emacs users who are new to Org-mode.
>
> This is basically covered by the manual. Period.
>
> 2. People new to Emacs who might want to use it /because/ of Org-mode.
>
> Here we have a huge potential for improvement, so to speak;).
>
> A couple of thoughts:
>
> - Screencasts and videos might be a viable option (even though it is a
> bit old, I consider your Google lecture a very good introduction to
> Org-mode - a survey of features; it is, however, aimed more at a
> power user than a newbie).
> - What might be really interesting would be something along the lines
> of C-h t. In fact, the Emacs tutorial itself badly needs an update
> imho. And a similar thing for Org-mode might be even better. In
> fact, though I am quite busy at the moment, I'd be happy to start
> thinking about something like this in my free time. What do you
> think?
> - For new users, there might be an installation instruction /including/
> installing Emacs (especially on Windows machines, where it might be
> tricky). I think it should be emphasized that (at least in case of
> Org-mode) Emacs may be treated more as an application framework,
> which incidentally has more text-editing capabilities than, say, edit
> boxes of GTK etc. (just a bit more, you know;)), and that Org-mode is
> an application running in this particular environment. (Calling it an
> Elisp Virtual Machine might be a bit stretching, though;).)
> - Last but not least: we are still waiting for Sacha Chua to draw a
> sketchnote-based intro to Org-mode;).
Hi Marcin,
thanks for your input!
However, for now, O was not asking for new material to be
produced (even though that may be interesting as well),
but rather I wanted to make a selection of the large
numbers of talks, screencasts, tutorials that introduce
into Org more progressively. For example, my talk at
Google is too long as the first thing a newbie should
encounter. I was hoping we can identify maybe 5 different
things (screencasts, tutorials, whatever) that we advertise
at the top of the tutorial page as the recommended default
introduction into Org. The rest of the tutorial page is then
still there as additional reference for people who stay and want
to dig deeper. The problem I have with the tutorial page
right now is that there is a huge amount of tutorials,
and no guidance for beginners.
- Carsten
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2013-09-28 10:09 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 [this message]
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
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=68CAD3FD-52FD-4D7D-A4BA-E4823F57E506@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mbork@wmi.amu.edu.pl \
/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).