emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: TEC <tecosaur@gmail.com>
To: Maxim Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Website revamp?
Date: Wed, 05 Aug 2020 20:03:43 +0800	[thread overview]
Message-ID: <87y2mt2s8v.fsf@gmail.com> (raw)
In-Reply-To: <rge6q8$ddi$1@ciao.gmane.io>


Thanks for stepping through your thoughts in such detail.
I really appreciate it :)

Maxim Nikulin <manikulin@gmail.com> writes:

> On a phone I would expect to see something like
>
> Org mode for GNU Emacs
>
> - Keeping notes
> - maintaining TODO lists
> - planning projects
> - authoring documents
>
> with a fast and effective plain-text system

I'll do a bit more on the banner design in a day or two, I'll play around a bit
then. Worst case that sort of content would be just under the banner on mobile
devices --- I really want to avoid a 'crammed' look.

> Sorry, but "An innovative and intuitive plain text markup syntax" means nothing
> to me. "Created by Carsten Dominik in 2003" is a sign of mature and stable
> enough software without disgusting "since ..." but contradicts a bit with
> "innovative".

Good to know. I'd be interested in hearing more thoughts on this, but for now
here are my own:
 - innovative :: does 'new' and exciting things that similar products don't
 - intuative :: despite doing a lot, it isn't complex to work with, but
   thoughtfully designed to be easy to use
 - plain text markup sytax :: what Org is ... mostly

I personally don't find 2003 at odds with "innovative". Something can both
have competitive advantages, and be mature.
   
Please let me know if this explanation of my view affects your own.
   
> In a "full" version my suggestion is to minimize amount of text significantly
> larger than 1em. 4em is excessively huge font for normal monitor. I am in doubt
> it is feasible to require readable but not oversized font on mobile devices,
> 1366x768px laptops, and 4k monitors simultaneously.

I take it you mean 1em to be the body text size, and are just referring to the
size of headings? Or do you mean 1rem?
The body text is currently ~1.2rem FYI.

> On the other hand, I hope, donate links work but in new design thy are not
> contrast and eye catching enough despite their colors.

Interesting that you should say this, personally I find them more eye-catching
than the current grey box in the corner.

I'm also planning on repeating that "Created ... support ..." banner on the
other pages, perhaps as a footer --- I haven't worked out the details yet.

If the colour needs to be more prominent, we could turn the styling from links
to buttons, but I suspect the change wouldn't be worth it.

> In my opinion on a laptop/desktop screen the banner should not occupy so much
> vertical space. I like the idea of adaptive one or two column layout depending
> of screen width that you have shown in another message.

I'll look forward to hearing your comments after I get around to implementing
that :)

> I see 3 category of users requiring content different to some extent but should
> be easily recognizable:
>
> - Newcomers need to recognize if org-mode is able to do what are they looking
> for. So features should be presented for them, they should notice links to docs
> and an instruction how to try it
> - "Help desk stuff" in a broad sense who are not aware of org-mode but have to
> help some person when local org-mode guru is not available. They need to quickly
> recognize what is org-mode is at all, so they may look for general descriptions,
> docs, specific discussion groups. Unsure but even "Download" instead "Install"
> might be more noticeable.
> - Experienced users are more or less familiar with the site, they may look for
> project news, hacks, how to debug particular issue or to submit a patch. They
> should be able to find info on not so often used feature or to find specific
> place in docs to send a link to a friend. Unfortunately I am not familiar enough
> with content of the site to recommend "hot" links to the main page.

Mmmm. This is a good point. The essential details are communicated by the
current large banner IMO

- plain text markup syntax
- versatile
- a few use cases
  + keeping notes
  + todo lists
  + planning
  + writing
- system

My current idea is to have the banner be a quick "what is it?", then have
elaboration as the first part of the content, links to other important parts of
the site (e.g. features, install) and little details like latest version and
release date after that.

> Priority of content is different for mobile and laptop/desktop visitors but the
> latter should see content, not just banner and void on the home page. There is
> room for improvement of current home page, but it is more informative than the
> new design demo.

Let's see how this is with the revised banner :)

>> Are you saying that you find the current mention of Emacs in the instillation
>> page works well?
>
> I do not remember how I realized that org-mode is a part of .deb package when I
> decided to try org-mode for the first time. I tend to believe that is not
> immediately clear that first paragraph could be just an alternative to second
> one. Maybe it should be emphasizing with headers:
> "Use org-mode bundled with Emacs" vs. "Install latest stable org-mode package
> from ELPA".

I think Ill try to work in a direct mention of Emacs in the banner.

> Please, fix a typo. Should be "Installation".

Fixed :D (on my local copy)

>> 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.
>
> It would be great but it requires more work.

I'll try to start with one, and see if the community steps up :)

> Minor remarks:
> - Should not be logo + "Org mode" in the navigation bar a link similar to
> "Home"?

Sounds reasonable, I'll tweak that.

> - I am afraid that without clear sign that demo page is an experiment, results
> in search engines could be distorted. Red block with text like "See official
> site https://orgmode.org" and robots.txt file could help to avoid confusion of
> people and crawlers.

Yea, no chance of that being an issue. For starters I don't think this is even
listed, but even if it was, with no links to the site it should be settled quite
firmly at the bottom of the last page :P


  reply	other threads:[~2020-08-05 12:27 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
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 [this message]
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=87y2mt2s8v.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).