Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: Change in policy on News?
Date: Mon, 9 Jan 2006 21:11:48 +0100
Message-ID: <6BCB9D8A16AC4241919521715F4D8BCE92E9A4@algol.sollentuna.se>
Thread-Topic: [pgsql-www] Change in policy on News?
Thread-Index: AcYVV0jDPPdtKV3WT1uNGOgP9RaWEAAAHigg
From: "Magnus Hagander" <mha@sollentuna.net>
To: "Marc G. Fournier" <scrappy@postgresql.org>,
	"Josh Berkus" <josh@agliodbs.com>
Cc: <pgsql-www@postgresql.org>

> > I'd love this, but it would require a site design change.  If you=20
> > remember, we'd talked about dividing the news tickers into=20
> 4 parts:  News, Product
> > Announcements, Events and Training.   However, that didn't=20
> work with the
> > design for the home page.
>=20
> How much work would it be to fix up the right column on the main page?
>=20
> Initial thoughts:
>=20
>    Get rid of the individual dates ... change it to something like:

I think that's a really bad idea, for two reasons:
1) It's good to know the exact date, when you're a frequent browser
2) We more or less *have* to keep up the throughput. And the list isn't
"dynamic" enough - once the first entry goes in for february, it gets to
live alone..

WRT keeping a separate list of product news, the question is do we
really mind if the right side piece gets longer. Yes, it would mean that
events scroll off the main page for smaller screens (like my laptop
screen at 768 lines), but you'd probably still see the header and the
top event, so you'd know to scroll. We could also limit both number of
and length of "product announcements", so that piece would be smaller
than the current ones.

//Magnus