From: Peter Eisentraut <peter_e@gmx.net>
To: pgsql-hackers@postgresql.org
Subject: Re: navigation menu for documents
Date: Wed, 15 Jul 2009 13:33:02 +0300
User-Agent: KMail/1.11.2 (Linux/2.6.26-2-686; KDE/4.2.4; i686; ; )
Cc: Richard Huxton <dev@archonet.com>, Andrew Dunstan <andrew@dunslane.net>,
	Dimitri Fontaine <dfontaine@hi-media.com>
References: <4A5CE7EB.20809@pgexperts.com> <4A5D10AD.6060305@dunslane.net>
	<4A5D1464.4040202@archonet.com>
In-Reply-To: <4A5D1464.4040202@archonet.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200907151333.02260.peter_e@gmx.net>

On Wednesday 15 July 2009 02:27:32 Richard Huxton wrote:
> Andrew Dunstan wrote:
> > Richard Huxton wrote:
> >> Andrew Dunstan wrote:
> >>> Yes, really. What you suggest here is just not adequate, IMNSHO. I
> >>> don't want to have to scroll to the top or bottom of the page to get
> >>> navigation, and I want to be able to see the navigation and go where
> >>> I want directly.
> >>
> >> Are you talking about the online manuals, or something else here?
> >
> > I don't care if we don't provide this for the online manuals on
> > postgresql.org - I'm quite happy to install it on my own server if
> > necessary. But I am talking about the HTML docs that come from our /doc
> > directory. And I bet if we had the option of better navigation, our
> > online users would want us to provide it.
>
> Shouldn't be too hard to come up with something reasonable with a little
> css. Something only activated if javascript is turned on or some such.
> Give me 48 hours and I'll have a play.

You just have to generate the full ToC on every HTML page and then use the 
right CSS to make it float where you want it.  I suspect that that method 
might make the build very slow, though.