Re: Emacs Newbie Info Pages

[Eli Zaretskii <eliz@gnu.org>]

> From: Summer Emacs <summeremacs@summerstar.me>
> Date: Fri, 13 Sep 2024 13:20:33 +0200
> Cc: Corwin Brust <corwin@bru.st>,
>  emacs-devel@gnu.org
> 
> Let me give you an example of what I think is a GOOD thing which teaches about Emacs: The Emacs
> Movement/Keys Tutorial. I think that’s a great tutorial. I understood it. It was easy to follow, and easy to use,
> and I learned it in no time. Whomever wrote that was great at that job. I want to emulate that for other stuff:
> Start from the point of view that the user doesn’t know the first thing about anything, and take them through
> some of the following:
> 1) What Emacs is and how they will learn it step by step.
> 2) Configuration
> 3) Themes (emphasise that they can make it look like they want to but here are a few examples of themes you
> can try out right now and where to get more and try those out)
> 4) Packages (We will want to list the major ones for writing/note taking. Org-Mode, EWS, Denote, Org-Roam,
> Fontaine because fonts are important to people, and Olivetti are some of the ones I’m thinking about.)
> There will be more packages listed, and please read what I wrote in my rough draft to cover the fact that we
> are not favouring certain packages over others:
> 
>  Emacs has so many packages available from so many people that they can't really all be counted. But
>  rest assured: it numbers in the thousands. Since the assumption for those reading this tutorial is that
>  they are not coders or developers, we are going to focus mostly on packages which will help you get up
>  and running with your writing needs. Here are some suggested packages. There are many more which
>  are not covered here and this is not necessarily an endorsement of one package over another. These
>  are just helpful starting places for new users.
> 
> I know that this will be contentious, just like our choosing certain themes and some minimalist configs, but
> look: we have to start someplace. And we have to make editorial decisions.
> 
> What do you think?

I think you should write the document and post it, and we can then
take it from there.  This would be a good progress, IMO.

> Also, if anyone else wants to collaborate on the document, I’m absolutely willing to do that
> and I’m even hoping for it. Please let me know how to go about sharing this with others who are interested in
> doing this. Do we set up a private email list? Do we collaborate on a git somewhere? I’m not sure how it all
> works and I’m willing to learn. But I do want to get this done sometime. =)

It's basically up to you, I think.  If you want to set up a repository
(preferably not GitHub, but if you must, that could also do), that's
okay as a starting point.  We can leave the decision of how to proceed
to later.