[GRASS-dev] Structure of links for addons, manual pages etc.

[Vaclav Petras]

Hi,

I think we need to rethink the structure of addresses/links to various
things which we are putting online.

The motivation are discussions "Linking Addons manual pages to core
modules", "addons for windows", and "Addon manual pages not linked".

For example, so far we were linking the trunk documentation using
grass70/manuals but since we forked the 70 branch these links now points to
it and not to trunk. Also all general links to GRASS documentation leads to
grass64/manuals but this will be soon very obsolete.

A lot of projects uses links such as latest, release or current (e.g.
latest/manuals or release/manuals) which leads to the current (latest)
release. And also links such as master, latest, trunk, nightly which leads
to the one builds from the source code of the main branch. Alternatively,
there is no special link for the current release which shortens URLs. I
think something like this might be beneficial for us.

So far I identified this set of things:

* GRASS binaries
* addons for MS Windows
* addons SVN
* manual pages
* programming manual (or manuals)

I don't have any concrete suggestion now. What are your experiences with
this?

Thanks,
Vaclav


http://lists.osgeo.org/pipermail/grass-dev/2014-April/068192.html
http://lists.osgeo.org/pipermail/grass-dev/2014-April/068193.html
http://lists.osgeo.org/pipermail/grass-web/2013-December/004587.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20140409/da59b6b7/attachment.html>