Re: [Firebird-website] Stable links to LangRef documentation

[Paul V. <pa...@vi...>]

Hi all,

> > We can do the same for documentation, but who will maintain links after
> > new docs release?
> >
> > It should be constant process to keep links and redirects up to date,
> > and I doubt that web development team can do it, because it's not in our
> > scope.
>
> I was thinking about this being automatic. Docs structure is known,
> the links can be either hashtable or two-way as well (link==>document
> and vice versa, based on i.e. topic heading).

It's certainly possible, but it may cost a lot of time to set this up (*), and who is going to do this? Also, the docs structure is not cast in concrete. Sometimes things change from version to version, so some kind of human monitoring and maintenance will be necessary.

I also wonder how big the advantage would be for our users and if it's worth it. Sometimes I google on a MySQL function and the first hit takes me to the documentation, but of the "wrong" version. If that's a problem, I go to the right version via the documentation index. Or I include the version number in the search to begin with.

What you propose is a nice feature, but I don't think the benefit will be huge. That said, if anybody wants to investigate and maybe implement it, please do! I'll be happy to help with information, but I'm no going to work on it myself.


Cheers,
Paul Vinkenoog


(*)
To give you an idea: the 2.5 LangRef Update alone consists of 256 separate web pages, most of them with a bunch of internal link targets as well. And that's just one of our many docs.