public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Peter Eisentraut <[email protected]>
Cc: Chris Meller <[email protected]>
Cc: PostgreSQL-documentation <[email protected]>
Subject: Re: Change to documentation headers
Date: Fri, 4 Feb 2011 16:23:34 -0500 (EST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Peter Eisentraut wrote:
> On ons, 2011-02-02 at 20:13 -0500, Bruce Momjian wrote:
> > Peter, based on feedback we have received, I think our users want our
> > docs header to look the same as our docs footer, i.e. few people see
> > the value of Fast Forward and Fast Backward, and they want "Up" to be in
> > the header.  You seem to have done all the substantive changes to
> > stylesheet.dsl --- would you make these changes?  Thanks.
> 
> I'll look into it.
> 
> Taking the same layout for the header navigation as for the footer
> navigation is not a problem.  But the top also shows the current chapter
> title.  Note sure if we want to lose that or show it somewhere
> different.

Thanks.  I studied stylesheet.dsl but was unable to understand how to
modify it.

Looking at the 9.0 docs now:

	http://www.postgresql.org/docs/9.0/static/tutorial-fk.html

I do like the chapter title there.  

Looking at "Home", we actually have two of them.  The "Home" at the top
left of the page links to the PG homepage, while the "Home" at the
bottom goes to the top of the 9.0 documentation.  That seems odd.  Maybe
we need to remove the "Home" at the bottom, or rename it.

You could get away with changing "Fast Backward" to "Up" and removing
"Fast Forward".

-- 
  Bruce Momjian  <[email protected]>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

view thread (19+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Change to documentation headers
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox