Hi! When people go to www.krusader.org, at top right of the page they see a [Documentation link](https://krusader.org/documentation/index.html) that brings them to really old information (about Krusader 2.4.0), unlike the new [Krusader handbook](https://docs.kde.org/trunk5/en/extragear-utils/krusader/index.html). Note: Maybe there a way so that https://krusader.org/documentation/index.html (which is stored in git://anongit.kde.org/websites/krusader-org.git) gets updated when someone changes the Krusader docbook files (which are stored in https://cgit.kde.org/krusader.git/tree/doc). Thanks!
(In reply to Toni Asensi Esteve from comment #0) > Note: Maybe there a way so that > https://krusader.org/documentation/index.html (which is stored in > git://anongit.kde.org/websites/krusader-org.git) gets updated when someone > changes the Krusader docbook files (which are stored in > https://cgit.kde.org/krusader.git/tree/doc). Sure, there is a way (meinproc5 index.docbook) but why we should store the data in both places at the same time? docs.kde.org proposes PDF for printing and global search, btw. So I find it's reasonable to remove docs from the site repo and replace them with a link (or two, with PDF) to automatically updated versions (once in a week) from d.k.o.
> Sure, there is a way (meinproc5 index.docbook) but why we should store the > data in both places at the same time? Maybe there is an advantage for visitors, but there are other factors that must be taken into account (like the "docs.kde.org proposes PDF for printing and global search, btw") ones that you wrote. > So I find it's reasonable to remove docs from the site repo and replace them > with a link (or two, with PDF) to automatically updated versions (once in a > week) from d.k.o. I find it better, too :-)
Solved by Alex Bikadorov :-)