From: Summer Emacs <summeremacs@summerstar.me>
To: "Sławomir Grochowski" <slawomir.grochowski@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: "About Emacs" page
Date: Fri, 20 Sep 2024 09:57:52 +0200 [thread overview]
Message-ID: <7038AEF2-9694-4941-8784-580CC10B0EDD@summerstar.me> (raw)
In-Reply-To: <878qvmg67n.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]
> On Sep 20, 2024, at 09:00, Sławomir Grochowski <slawomir.grochowski@gmail.com> wrote:
>
> Summer Emacs <summeremacs@summerstar.me> writes:
>> Emacs Logo (as usual or changed - either way)
>>
>> —> New Emacs User? Click here. <--
>> Emacs Tutorial
>> Emacs Manual
>> Emacs Guided Tour
>> Ordering Manuals
>>
>> GNU and Freedom
>> Copying Conditions
>> Getting New Versions
>> Absence of Warranty
>>
>> Authors
>> Contributing
>
> Good work!
>
Thanks. Putting order in stuff is part of my job. 🙃
> 1. The new links order is definitely a good idea. I support it.
> 2. I also think the logo is ugly and might deter new users. But let's move
> this topic to another thread because there will be a long and heated
> discussion about personal preferences here. So let's first focus on
> improving the order of links.
Yea. I seem to have repeatedly hit the hornet’s nest with a very large stick with this topic. 🐝
> 3. Agree with others that the 'Click here' button doesn't fit with Emacs.
>
Yea, it stands out. I’ll give you that. It could just say “New Emacs User Tutorial”, but that would conflict a bit with the Emacs Tutorial right under it. Also, I know it’ll be seen as “new” as in “we didn’t do computers like that back in the day”, but most new users to apps expect a “click here” sorta thing. And I’m trying to reach them. So I’m open to how to do that. 🙃
> --
> Slawomir Grochowski
Summer Emacs ☀️🐃
summeremacs@summerstar.me
“Shake it Off <https://www.youtube.com/watch?v=M_JiMkVx0FU>” - Taylor Swift 💖
[-- Attachment #2: Type: text/html, Size: 4786 bytes --]
next prev parent reply other threads:[~2024-09-20 7:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 10:19 "About Emacs" page Summer Emacs
2024-09-19 12:57 ` Philip Kaludercic
2024-09-20 2:47 ` Emanuel Berg
2024-09-20 6:41 ` Eli Zaretskii
2024-09-20 7:09 ` Juergen Fenn
2024-09-20 7:41 ` Juergen Fenn
2024-09-20 7:52 ` Summer Emacs
2024-09-20 8:55 ` Emanuel Berg
2024-09-20 10:23 ` Eli Zaretskii
2024-09-20 12:23 ` Juergen Fenn
2024-09-20 8:34 ` Ulrich Mueller
2024-09-20 10:27 ` Eli Zaretskii
2024-09-20 15:52 ` Manuel Giraud via Emacs development discussions.
2024-09-20 17:34 ` Eli Zaretskii
2024-09-28 9:39 ` Eli Zaretskii
2024-09-28 10:55 ` Ulrich Mueller
2024-09-28 11:40 ` Eli Zaretskii
2024-09-22 4:09 ` Richard Stallman
2024-09-22 15:54 ` Philip Kaludercic
2024-09-24 3:31 ` Richard Stallman
2024-09-24 12:05 ` Philip Kaludercic
2024-09-20 7:00 ` Sławomir Grochowski
2024-09-20 7:57 ` Summer Emacs [this message]
2024-09-22 4:09 ` Richard Stallman
2024-09-22 5:26 ` Eli Zaretskii
2024-09-23 10:41 ` Summer Emacs
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7038AEF2-9694-4941-8784-580CC10B0EDD@summerstar.me \
--to=summeremacs@summerstar.me \
--cc=emacs-devel@gnu.org \
--cc=slawomir.grochowski@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.