Re: Alternate PostgreSQL.org Design

please note I am dropping -advocacy from this discussion since I need
some focus on www work

On Fri, 2004-11-12 at 04:22, Dave Page wrote:
> > -----Original Message-----
> > From: pgsql-www-owner(at)postgresql(dot)org
> > [mailto:pgsql-www-owner(at)postgresql(dot)org] On Behalf Of Omar Kilani
> > Sent: 12 November 2004 02:38
> > To: pgsql-www(at)postgresql(dot)org; pgsql-advocacy(at)postgresql(dot)org
> > Subject: [pgsql-www] Alternate PostgreSQL.org Design
> >
> > Hi Again,
> >
> > We would like to put forward an alternate design to the
> > current wwwdevel design.
> >
> > It is available at: http://postgresql.tinysofa.com/
> >
> > We believe that it is clean, professional and simple. And it
> > makes the release of 8.0 actually... exciting. :)
>
> Yes, it is a very nice design, far nicer than your last one :-)
>
> I am concerned though - after a long time looking around and discussing
> things on and off, we already all agreed on a design. I'm concerned for
> 2 main reasons:
>
> 1) We accepted a concept from Lukasz - I don't like the idea of throwing
> away his hard work in this way.
>

One problem I have with Lukasz design is that some of the subsection
really scream out for second level navigation.

In Lukasz design, we end up re-propogating the right nav bar on every
page which I think is bad because it uses a lot of screen real estate
while adding little/no substance to the secondary pages. For example, do
we really need a link to external community sites on every page?

In something like the "Overview" section, I would like to add in content
like case studies, gui tools, advantages, and other sections from
advocacy and techdocs websites, but this mean putting all of these
subsections on the main "overview" page, creating a long scrolling lists
that have to be gone through to find content. I think it is easier for
people to scroll short lists of subcategories in a left hand nav like in
the "About" section of the tinysofa design.

These underlying structural issues need to be addressed regardless of
what design we use.

> 2) What happens if xyz web design comes and offers us another great
> design next week. Do we start again? Where/when do we draw the line? If
> I'm honest, based on our agreement to use Lukasz' design I think that
> line should be drawn already.
>

If we agree that there are some underlying structural issues, then
either that needs to be addressed in the current design, or we need to
swap. I understand that we don't want to just toss Lukasz' work out the
window, but if we were developing an application and we found flaws in
some piece of it, and someone else coded up an alternative
implementation, I don't think we would discount the new idea simply on
the grounds that we already have an existing implementation. (In
fairness, the new design also has some structural issues, like fixed
width, that would also have to be addressed before we could use it)

Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL