emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: TEC <tecosaur@gmail.com>
To: Russell Adams <RLAdams@AdamsInfoServ.Com>
Cc: emacs-orgmode@gnu.org
Subject: Re: TEC: update the new website ML page?
Date: Tue, 15 Dec 2020 00:29:06 +0800	[thread overview]
Message-ID: <874kkopbd5.fsf@gmail.com> (raw)
In-Reply-To: <20201214162718.GC6352@maokai>

Russell Adams <RLAdams@AdamsInfoServ.Com> writes:

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

Hmmm. "Updates" seems like a bit of a special thing, but perhaps some
merging could happen sensibly. If that could be worked out, I'd
definitely be much more receptive to the idea of adding another link.

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

Oh good :)

> 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 do see your point. I think in order to warrant being presented as a
one-step-from-the-homepage target it would be good to tidy up the Worg

At the moment I suspect it would be a bit overwhelming to newcomers ---
everything splurged onto on page seems a bit much :P

How does that sound?


  reply	other threads:[~2020-12-14 17:07 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
2020-12-14 16:29       ` TEC [this message]
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:

  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=874kkopbd5.fsf@gmail.com \
    --to=tecosaur@gmail.com \
    --cc=RLAdams@AdamsInfoServ.Com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).