emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Joseph Vidal-Rosset <joseph.vidal.rosset@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode list <emacs-orgmode@gnu.org>
Subject: Re: Org Tutorials need more structure
Date: Sat, 28 Sep 2013 09:22:02 +0200	[thread overview]
Message-ID: <CAD-VTcG6qntdqrF6hQM1Espqt9M2BL_E0EgzhDsxGCWVpjAUvQ@mail.gmail.com> (raw)
In-Reply-To: <EF119E90-532F-4890-991C-0C55691A898E@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2411 bytes --]

Hi Dominik, hi everyone,

Thank you for org-mode and thanks to all who contribute to this project.

I am a newby to org-mode , I am an emacs user for LaTeX, mainly, and I
would be happy to use more and more emacs, so org-mode seems very
attractive.

I imagine that writing a tutorial is a big work and I hope that I will not
offend people who have taken this time. But I must say that the org-mode
manual and the tutorials that I have tried to read are not enough
progressive for beginners and do not take care of difference between
interests of people.

Example: I am presently mainly interested to see if it is possible to use
gnus to write a scientific letter with all conveniences of texlive. Of
course I can open a tex file with letter class and send to my colleague a
pdf file. But it would be more convenient to write an email and using
conversions to html and png images to send to him directly this email. I
guess it is possilbe to do it with gnus. But the documentation is esoteric:
I hear about links, but how it works concretly with example understanble by
a newby ...  mystery. It is therefore frustrating and quickly discouraging.

So, in my opinion, a good tutorial is divided into precise tasks and speaks
like that:
"You need to do that?  So, follow me , from step to step, I will going to
show you how I succeed to do what you want to do, and by imitation, you
will also succeed ! "  A good tutorial avoids to suppose that the reader is
already an expert.

In a word, too much tutorial in org-mode lack of pedagogical efforts.

Sorry to be speak so frankly, but I hope it will help.

Waiting your help with gnus - latex and conversion in html , etc. etc.

All the best

Jo.


2013/9/28 Carsten Dominik <carsten.dominik@gmail.com>

> 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
>

[-- Attachment #2: Type: text/html, Size: 3220 bytes --]

  reply	other threads:[~2013-09-28  7:22 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 [this message]
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
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=CAD-VTcG6qntdqrF6hQM1Espqt9M2BL_E0EgzhDsxGCWVpjAUvQ@mail.gmail.com \
    --to=joseph.vidal.rosset@gmail.com \
    --cc=carsten.dominik@gmail.com \
    --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).