From: TEC <tecosaur@gmail.com>
To: Maxim Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Website revamp?
Date: Tue, 04 Aug 2020 23:53:13 +0800 [thread overview]
Message-ID: <875z9y4cma.fsf@gmail.com> (raw)
In-Reply-To: <rgc00h$ed1$1@ciao.gmane.io>
Thanks for the feedback!
Maxim Nikulin <manikulin@gmail.com> writes:
> 03.08.2020 12:11, TEC wrote:
>>
>> To see how orgmode.org currently appears, see
>> https://i.imgur.com/XPFfBaB.png
>
> Sorry for negative (and maybe discouraging) feedback. I would
> not mind if you just skip my complains since I am not a
> contributor to org-mode.
Please, share your thoughts!
> Concerning the screenshot, when first impression, that
> everything is broken and do not worth reading at all, is over,
> in my opinion, the text makes much more sense than "innovative"
> marketing stuff got priority on the demo of the new design. I
> consider the list of tasks, that org mode could help with, is
> the most important thing to attract new users. It should just be
> properly formatted.
Re content for the index page, my current thoughts are:
- Some sort of informative introductory paragraph
- List of most common applications of org - Note latest version,
and when it was released
I also have a styled equivalent of the screenshot on the current
site.
These things just need to move from my mind, to the page :)
Do let me know if you have any other specific ideas on content for
the index.
> It seems that new variant is too mobile-centric. On a 24in
> monitor I expect something more than just a banner. There is
> plenty of room for brief news related to new releases, for more
> details of most important features (on the other hand I am
> against arbitrary scaled screenshots with excessively huge
> characters in comparison to surrounded text), etc. I am aware
> that my taste is against of modern design trends.
If you have specific suggestions on how I could smoothly work in a
better design for the index on the desktop, I'd love to hear them.
If you could pair any such suggestions with reference to my
earlier thoughts* on the purpose of each page that will make it
easier to glimpse your thought process, and how it compares to my
own.
\* see email in reply to Colin sent on Mon 03 Aug 07:53 UTC
> A couple of remarks unrelated to new look but should be
> addressed in the case of rework.
>
> I am surprised that Emacs is explicitly mentioned only in html
> head title. The relation should be clear for new visitors.
That's:
a) been removed from the head title. I couldn't find a browser
which would
display the whole thing without chopping it off the last
~third
b) going to be mentioned prominently in the body, at least in my
current thoughts
> As to installation, I believe that org-mode bundled with Emacs
> is more than enough for first try. It is a shorter path to
> become familiar with most prominent features just to start
> editing of an .org file (or to download a prepared demo .org).
> Getting the latest stable version could be a next step for the
> hooked users.
Are you saying that you find the current mention of Emacs in the
instillation page works well? I'm currently just linking to Emacs.
Looking at the page though, I think I should make a more prominent
action to download Emacs.
I love the idea of a demo org file! If anyone would like to help
out with creating one by sending in contenders / snippets that
would be brilliant!
Even better - having two or three different demo files based on the use case of
the new user - e.g. programmer, author, organisation - or something like that.
next prev parent reply other threads:[~2020-08-04 16:12 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 13:55 Website revamp? TEC
2020-07-30 13:00 ` TEC
2020-07-30 13:20 ` Russell Adams
2020-07-30 13:36 ` Amin Bandali
2020-07-30 14:19 ` TEC
2020-07-30 14:47 ` Bruce D'Arcus
2020-07-30 15:53 ` Amin Bandali
2020-07-30 17:22 ` Russell Adams
2020-07-30 17:57 ` TEC
2020-07-30 19:03 ` Russell Adams
2020-08-01 8:15 ` TEC
2020-08-02 18:08 ` TEC
2020-08-03 5:10 ` Colin Baxter
2020-08-03 5:11 ` TEC
2020-08-03 7:01 ` Colin Baxter
2020-08-03 7:53 ` TEC
2020-08-03 8:03 ` tomas
2020-08-04 5:54 ` Eric S Fraga
2020-08-05 10:17 ` Bo Grimes
2020-08-05 10:26 ` Eric S Fraga
2020-08-05 10:40 ` Bo Grimes
2020-08-05 10:43 ` TEC
2020-08-03 10:54 ` Gustav Wikström
2020-08-04 15:48 ` Maxim Nikulin
2020-08-04 15:53 ` TEC [this message]
2020-08-04 16:18 ` Bruce D'Arcus
2020-08-04 16:23 ` TEC
2020-08-04 16:30 ` Bruce D'Arcus
2020-08-05 11:56 ` Maxim Nikulin
2020-08-05 12:03 ` TEC
2020-08-06 11:25 ` Maxim Nikulin
2020-08-06 11:52 ` TEC
2020-08-24 7:43 ` TEC
2020-08-25 10:28 ` Maxim Nikulin
2020-08-25 12:02 ` TEC
2020-08-25 15:09 ` TEC
2020-08-27 16:09 ` Maxim Nikulin
2020-09-01 16:39 ` TEC
2020-09-30 16:24 ` Maxim Nikulin
2020-08-11 15:24 ` Maxim Nikulin
2020-08-04 15:53 ` Bruce D'Arcus
2020-08-04 16:09 ` TEC
2020-08-04 21:43 ` Bo Grimes
2020-08-05 15:24 ` Maxim Nikulin
2020-08-05 16:00 ` TEC
2020-08-07 5:19 ` David Rogers
2020-08-04 5:59 ` Eric S Fraga
2020-08-04 6:27 ` TEC
2020-08-04 20:44 ` gyro funch
2020-08-24 15:39 ` Maxim Nikulin
2020-07-30 19:40 ` Scott Randby
2020-09-01 16:44 ` TEC
2020-09-01 18:07 ` Tom Gillespie
2020-09-01 18:11 ` Tom Gillespie
2020-09-02 3:48 ` TEC
2020-09-02 2:59 ` TEC
2020-09-04 9:37 ` Bastien
2020-09-05 9:08 ` Martin Schöön
2020-09-05 10:16 ` Colin Baxter
2020-09-07 17:24 ` TEC
2020-09-07 18:13 ` TEC
2020-09-08 5:41 ` Tom Gillespie
2020-09-08 5:49 ` TEC
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=875z9y4cma.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@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 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).