9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] sources/contrib index
Date: Thu, 24 Nov 2005 19:54:30 -0500	[thread overview]
Message-ID: <ee9e417a0511241654u74d78dei44fd1ae2cb4727be@mail.gmail.com> (raw)
In-Reply-To: <20051124222518.GJ12975@server4.lensbuddy.com>

> [3] http://plan9.bell-labs.com/wiki/plan9/Mirrors/

Here is an important tip for writing wiki pages:
   *** explain what the point is ***

This page is a perfect example of a bad page.
It is just a collection of links with no explanation
of why you might want to click on those links
or what the bigger context is.

There should always be a couple of sentences
at the top of the page explaining what's going on.
It makes a huge difference in the usability of
the page, especially if one is following a hyperlink
in an email or external server and has no context
at all.

The problem is not limited to the above page.
Many pages suffer from this problem.

I try to clean these up as I see them, but I don't
always have time.

Thanks.
Russ


      reply	other threads:[~2005-11-25  0:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-24 22:25 Uriel
2005-11-25  0:54 ` Russ Cox [this message]

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=ee9e417a0511241654u74d78dei44fd1ae2cb4727be@mail.gmail.com \
    --to=rsc@swtch.com \
    --cc=9fans@cse.psu.edu \
    /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).