unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Summer Emacs <summeremacs@summerstar.me>
Cc: rms@gnu.org, suhailsingh247@gmail.com, corwin@bru.st,
	emacs-devel@gnu.org
Subject: Re: Emacs Newbie Info Pages
Date: Tue, 17 Sep 2024 18:44:27 +0300	[thread overview]
Message-ID: <867cbab7z8.fsf@gnu.org> (raw)
In-Reply-To: <D5F2886D-9618-47A2-95C2-2FD4123AA809@summerstar.me> (message from Summer Emacs on Tue, 17 Sep 2024 16:12:17 +0200)

> From: Summer Emacs <summeremacs@summerstar.me>
> Date: Tue, 17 Sep 2024 16:12:17 +0200
> Cc: rms@gnu.org,
>  suhailsingh247@gmail.com,
>  corwin@bru.st,
>  emacs-devel@gnu.org
> 
>  1) My proposal is for new people to have a landing set of pages to click through, explaining things
>  in a clear and easy way for them to understand without the instant introduction of concepts which
>  are alien to them. I think the help files are a great thing, but they are overwhelming for new
>  people. I know this because I’ve shown it to people in my circles who don’t know much of anything
>  about how to use a computer, but still use applications such as Word or Pages to type up things
>  for work/classes. They couldn’t understand the first thing about the help pages.
> 
>  I think Richard asked about the difference between what you propose
>  and the existing Emacs tutorial (which can be read by typing "C-h t").
>  The tutorial is not what you call "help files", and is written in a
>  different style and with different goals in mind.
> 
>  Or are you saying that the tutorial is also overwhelming, in
>  particular due to introducing too many alien concepts?  If so, that
>  might be worth a separate discussion, because the tutorial is not
>  supposed to be hard to read and understand.
> 
> I did mention the tutorial but I said I think it’s fantastic. I was speaking about the other help files in general.
> Such as clicking on the “Emacs guided tour” - it’s very non-newbie friendly. It’s a great resource but I think we
> need something better for brand new users who don’t have a coding background.

OK, but then Richard's question still stands, and it would be good to
hear your view on the difference between what you propose and the
tutorial.  Because I could think about a few follow-up questions, such
as:

  . can we extend the tutorial with the information you would like to
    have in the document you propose?
  . maybe make what you propose to be "tutorial, part2"?
  . or how about a tutorial whose audience is non-programmers?

etc.



  parent reply	other threads:[~2024-09-17 15:44 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 17:30 Emacs Newbie Info Pages Summer Emacs
2024-09-12 18:26 ` Philip Kaludercic
2024-09-12 18:45   ` Summer Emacs
2024-09-12 19:17     ` Philip Kaludercic
2024-09-13  6:40       ` Eli Zaretskii
2024-09-13  7:36         ` Philip Kaludercic
2024-09-13  7:39       ` Summer Emacs
2024-09-13 14:46         ` Juergen Fenn
2024-09-13 12:28       ` Thanos Apollo
2024-09-12 18:29 ` Corwin Brust
2024-09-12 19:00   ` Summer Emacs
2024-09-13  2:24   ` Suhail Singh
2024-09-17  3:47     ` Richard Stallman
2024-09-17 10:58       ` Summer Emacs
2024-09-17 13:31         ` Eli Zaretskii
2024-09-17 14:12           ` Summer Emacs
2024-09-17 14:48             ` Emanuel Berg
2024-09-17 16:45               ` Summer Emacs
2024-09-18  1:09                 ` Emanuel Berg
2024-09-17 15:44             ` Eli Zaretskii [this message]
2024-09-17 16:49               ` Summer Emacs
2024-09-17 17:53                 ` Eli Zaretskii
2024-09-19  3:51         ` Richard Stallman
2024-09-19  9:45           ` Summer Emacs
2024-09-13  6:38   ` Eli Zaretskii
2024-09-13  7:45     ` Summer Emacs
2024-09-13 10:46       ` Eli Zaretskii
2024-09-13 11:20         ` Summer Emacs
2024-09-13 11:57           ` Eli Zaretskii
2024-09-13 12:09             ` Summer Emacs
2024-09-13 13:31               ` Eli Zaretskii
2024-09-18  8:13       ` Emanuel Berg
2024-09-18 20:02         ` Juergen Fenn
2024-09-20  2:39           ` Emanuel Berg
2024-09-22 12:37   ` Peter Oliver
2024-09-22 14:31     ` Eli Zaretskii
2024-09-13  6:35 ` Eli Zaretskii

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=867cbab7z8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=corwin@bru.st \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=suhailsingh247@gmail.com \
    --cc=summeremacs@summerstar.me \
    /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.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).