Simon Kitching wrote:
On Sat, 2005-05-21 at 09:46 +0100, Stephen Colebourne wrote:
2) Related (to the user picking the first URL), I suggest that the URL
should be of the full form for a project (named foo) right down to
trunk. Again, this will help people who just pickup the link and don't
read the text. Then, the rest of the page can explain other URLs, and
their purposes.
How can this be done? The page here is just a static page within
commons-build...
You misunderstand ;-) I mean, to use the name foo on the static page, as
an example.
That way, they have to change the URL to make it work (substitute lang
for foo etc.). That might make them more likely to read the text.
Also, there is less chance of them checking out the branches and tags.
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
