Some manual pages lack links to GitHub source

[jidanni]

Pages like

• https://grass.osgeo.org/grass78/manuals/g.gisenv.html

have a link at the bottom to

• ​https://github.com/OSGeo/grass/tree/master/general/g.gisenv

Alas, pages like

• https://grass.osgeo.org/grass78/manuals/variables.html

lack a link at the bottom to

• ​https://github.com/OSGeo/grass/blob/master/lib/init/variables.html

or perhaps to .../tree/master/...

[jidanni]

E.g.,

• https://grass.osgeo.org/grass78/manuals/grass7.html lacks link to
• ​https://github.com/OSGeo/grass/blob/master/lib/init/grass7.html

[wenzeslaus]

Right, this is done only for modules. The link is really not to the HTML but to the source code of corresponding module. Source code for a module is a directory with source code (one or more files) and HTML documentation (and a Makefile).

The grass7.html page has a corresponding source code which is either ​grass.py or the ​lib/init directory.

However, some pages do not have any specific source code associated with them. I don't see where variables.html should point to.

Perhaps creating a list of those which are missing and what should be linked there would be helpful. I think we will need to go back and forth to figure out if there is something or not or if there is some general rule like for the modules.