emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: TEC: update the new website ML page?
Date: Mon, 14 Dec 2020 17:27:18 +0100	[thread overview]
Message-ID: <20201214162718.GC6352@maokai> (raw)
In-Reply-To: <878sa0pemm.fsf@gmail.com>

On Mon, Dec 14, 2020 at 11:37:09PM +0800, TEC wrote:
> Hi Russel, while I appreciate the significance of Worg, I currently
> don't feel that adding it to the header improves the site.
>
> There are two concerns I have on this.
>
> 1. I'm very wary of "header creep", see https://0x0.st/iFS7.png for a
>    mock up of an "extreme" example.
>    IMO the current state is "bulging", with 4-6 items as the ideal.
>    Adding Worg would take us to 8. In addition to the increased number
>    of visual elements, it also lessens the individual significance of
>    the per-existing items. If a "features" item has 3 other items, it is
>    much more emphasised than when it has 7 other items.
>
>    This is just a long winded way of me expressing the view that adding
>    to the header affects the perception of the rest of the header, and
>    thus the overall effect may be negative, as I suspect it would be in
>    this case.

One could argue that "Releases", "Updates", and "Install" should be
merged into a common download link. They all are the same thing. ;]

I completely agree with you that not everything can live in the
header.

However Worg is a key component because it's community maintained
documentation. Not just anyone can upload to the main site, but Worg
is as "wiki" as we have. As an integral part of the community
supported documentation I thought it should be in the header.

I'm not suggesting any other header spam. ;]


------------------------------------------------------------------
Russell Adams                            RLAdams@AdamsInfoServ.com

PGP Key ID:     0x1160DCB3           http://www.adamsinfoserv.com/

Fingerprint:    1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3


  parent reply	other threads:[~2020-12-14 16:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 10:45 TEC: update the new website ML page? Russell Adams
2020-11-16 17:10 ` Tom Gillespie
2020-12-14  6:46 ` Bastien
2020-12-14 15:37   ` TEC
2020-12-14 16:09     ` Eric S Fraga
2020-12-14 16:10       ` TEC
2020-12-14 16:27     ` Russell Adams [this message]
2020-12-14 16:29       ` TEC
2020-12-14 18:14         ` Russell Adams
2020-12-14 18:20           ` TEC
2020-12-14 19:45             ` Russell Adams

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=20201214162718.GC6352@maokai \
    --to=rladams@adamsinfoserv.com \
    --cc=emacs-orgmode@gnu.org \
    /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).