Hi devs,
still our (Google) ranking of the G7 manual is fairly bad (ideas
welcome how to fix that).
For the time being I have added a HTML injection to the cronjob which
creates the G6 manual pages.
Each page now contains a box, pointing the user to G7.
Markus
On 18-08-16 10:22, Markus Neteler wrote:
Hi devs,
still our (Google) ranking of the G7 manual is fairly bad (ideas
welcome how to fix that).
I am not a developer, just something I wondered; why not having one permanent address for the manual, which always reflects the latest stable release, and if needed, from there add links to older versions? Obviously not a solution for now, but this would lead, in the future, to more stable and permanent rankings for the most up-to-date version.
For the time being I have added a HTML injection to the cronjob which
creates the G6 manual pages.Each page now contains a box, pointing the user to G7.
Very helpful
Markus
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
On Thu, Aug 18, 2016 at 11:50 AM, Paulo van Breugel
<p.vanbreugel@gmail.com> wrote:
On 18-08-16 10:22, Markus Neteler wrote:
Hi devs,
right:
s+devs+all+
still our (Google) ranking of the G7 manual is fairly bad (ideas
welcome how to fix that).I am not a developer, just something I wondered; why not having one
permanent address for the manual, which always reflects the latest stable
release, and if needed, from there add links to older versions? Obviously
not a solution for now, but this would lead, in the future, to more stable
and permanent rankings for the most up-to-date version.
+1
Perhaps simply this:
https://grass.osgeo.org/manuals/
https://grass.osgeo.org/manuals/addons
I could easily add that in the CMS and make it point to the current
stable version.
For the time being I have added a HTML injection to the cronjob which
creates the G6 manual pages.Each page now contains a box, pointing the user to G7.
Very helpful
Good!
Markus
On Thu, Aug 18, 2016 at 5:54 AM, Markus Neteler <neteler@osgeo.org> wrote:
> I am not a developer, just something I wondered; why not having one
> permanent address for the manual, which always reflects the latest stable
> release, and if needed, from there add links to older versions? Obviously
> not a solution for now, but this would lead, in the future, to more
stable
> and permanent rankings for the most up-to-date version.+1
Perhaps simply this:
https://grass.osgeo.org/manuals/
https://grass.osgeo.org/manuals/addonsI could easily add that in the CMS and make it point to the current
stable version.
If we can maintain the URL in the long term that would be great.
BTW, surprised to see "keywords index" as part of the "manuals" page.
Unfortunately the links are broken:
https://grass.osgeo.org/v.hull.html
Anyway, the above solution is better if we can have link like:
https://grass.osgeo.org/manuals/v.hull.html
https://grass.osgeo.org/manuals/v.hull
There is potential conflict of:
https://grass.osgeo.org/grass70/manuals/grass7.html
https://grass.osgeo.org/grass70/manuals/grass7
https://grass.osgeo.org/grass70
https://grass.osgeo.org/manuals/grass7.html
https://grass.osgeo.org/manuals/grass7
but if the command will be `grass7` (or even `grass`) and the version
always two numbers and the order is not changed to "manuals/grass70", no
conflict will happen.
Vaclav
On Thu, Aug 18, 2016 at 2:53 PM, Vaclav Petras <wenzeslaus@gmail.com> wrote:
On Thu, Aug 18, 2016 at 5:54 AM, Markus Neteler <neteler@osgeo.org> wrote:
> I am not a developer, just something I wondered; why not having one
> permanent address for the manual, which always reflects the latest
> stable
> release, and if needed, from there add links to older versions?
> Obviously
> not a solution for now, but this would lead, in the future, to more
> stable
> and permanent rankings for the most up-to-date version.+1
Perhaps simply this:
https://grass.osgeo.org/manuals/
https://grass.osgeo.org/manuals/addonsI could easily add that in the CMS and make it point to the current
stable version.If we can maintain the URL in the long term that would be great.
+1
BTW, surprised to see "keywords index" as part of the "manuals" page.
It was an attempt to tell the CMSMS to index the manual pages. Seems
not to work.
Unfortunately the links are broken:
Internally it is this "user tag" in CMSMS:
print file_get_contents("http://grass.osgeo.org/grass72/manuals/keywords.html"\);
which seems to eat the path. Ideas?
Anyway, the above solution is better if we can have link like:
https://grass.osgeo.org/manuals/v.hull.html
https://grass.osgeo.org/manuals/v.hull
Yes.
There is potential conflict of:
https://grass.osgeo.org/grass70/manuals/grass7.html
https://grass.osgeo.org/grass70/manuals/grass7
https://grass.osgeo.org/grass70
https://grass.osgeo.org/manuals/grass7.html
https://grass.osgeo.org/manuals/grass7but if the command will be `grass7` (or even `grass`) and the version always
two numbers and the order is not changed to "manuals/grass70", no conflict
will happen.
Two numbers would always solve it.
Markus