> One of the other problems that always arises is "what version(s) does
> this document apply to?" Typically its out of date, but the new user
> doesn't really know that. So I thought of a possible way to=20
> address this
> and put up an example for you all to kick around and see if it has any
> merit. The general idea is that whenever you write a new page=20
> or update
> an existing one, you put a line across the top which shows the
> applicable versions. If the page replaces and older one, you put an
> "Older" link on the left end of this line. When this page is=20
> you put a "Newer" link on the right end of the line. The page which
> represents the most recent released version which has been documented
> should get included in the proper wiki Category.
> I know this won't make people any more likely to keep=20
> documents current,
> but at least everyone knows what versions they were written for.
> to see an example go to:
> and follow the "Web Pages" link. This leads to a description of the
> search page for 1.3.2 - 1.3.7. Newer (1.3.8/trunk) and older (1.2.x)
> pages are available with the newer/older links.
Now that, sir, is excellent. I had, in the past, an idea about using
icons saying "New in <VERSION>" and attaching them liberally through the
wiki, but your idea is much cleaner, simpler, and easier to use. +1
from me; let's call it a standard and start using it. There will need
to be some discipline about naming pages, but I think we can manage that
as it happens (_<version>) is good, with hyphens or .x as required).
We'll have to move/rename pages occasionally; when we do, leaving a
pointer to the new page (or the "latest") is best.
Attention: The information contained in this message and/or attachments
from AgResearch Limited is intended only for the persons or entities
to which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipients is prohibited by AgResearch
Limited. If you have received this message in error, please notify the