ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Alan Stone" <software.list.1es9s@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Reorganization of the main page
Date: Wed, 27 Aug 2008 10:22:43 +0200	[thread overview]
Message-ID: <326847810808270122h7d2b41d9y94d7e83d116cd427@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0808260613430.1696@nqv-yncgbc>

It has a much better structure indeed.

Missing the wiki-only search feature though.

Placing the texshow-web and mail archive links in a more relevant
section, instead of hidden in the wiki's left column, would be welcome
- especially for newbies.

Also, when a newbie reads "texshow-web" (s)he doesn't have a clue what
that means. It's geek talk. Better say something like "ConTeXt
commands directory" or something else that's meaningful, relevant and
useful for them.

Samewise:

- live context
- download
- download area

All these don't mean a thing to somebody who sees this page for the first time.

Live ConTeXt ? What's that ? A live recording of a band named ConTeXt
? (joking ;O)

Download and download area? What's the difference ? As a newbie I
don't want to have waste my time and click on every link to find out
what's behind it. Tell me from the link itself what it means, what's
behind it so I can find what I'm looking for and get up to speed asap.

As for the logo...

Who cares ?

Logo's don't enable people to figure out how to use software and be
productive with it.

The proof is in the pudding, not in the logo.

Hope that helps.

Best,
Alan
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2008-08-27  8:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26 10:19 Aditya Mahajan
2008-08-26 21:11 ` Andrea Valle
2008-08-27  2:03 ` Yue Wang
2008-08-27  8:48   ` Patrick Gundlach
2008-08-27 11:10     ` Mojca Miklavec
2008-08-27 18:35     ` Henning Hraban Ramm
2008-08-27  7:49 ` Marcin Borkowski
2008-08-27  8:22 ` Alan Stone [this message]
2008-08-27  9:14   ` Patrick Gundlach
2008-08-27  9:20     ` Marcin Borkowski
2008-08-27  9:53       ` Eric DÉTREZ
2008-08-27 10:00         ` Taco Hoekwater
2008-08-27  9:26     ` Flavien Lambert
2008-08-27  9:34       ` Marcin Borkowski
2008-08-27 18:38       ` Henning Hraban Ramm
2008-08-27 10:33     ` Alan Stone
2008-08-27 10:54       ` Jörg Hagmann
2008-08-27 11:13       ` Mojca Miklavec
2008-08-27 16:25       ` Patrick Gundlach
2008-08-27 16:55         ` Alan Stone
2008-08-28 15:51         ` Patrick Gundlach
2008-08-28 21:25           ` Mojca Miklavec
2008-08-27 11:30 ` Mojca Miklavec
2008-08-28  8:52   ` Yue Wang
2008-08-27 16:00 ` Mohamed Bana
2008-08-28 20:35 ` Aditya Mahajan
2008-08-29  5:33   ` Marcin Borkowski

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=326847810808270122h7d2b41d9y94d7e83d116cd427@mail.gmail.com \
    --to=software.list.1es9s@gmail.com \
    --cc=ntg-context@ntg.nl \
    /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.
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 NNTP newsgroup(s).