From: Josh Berkus <josh@agliodbs.com>
Organization: PostgreSQL @ Sun
To: pgsql-www@postgresql.org
Subject: Re: Training events policy ... first test case
Date: Wed, 24 Oct 2007 08:56:35 -0700
User-Agent: KMail/1.8.2
References: <200710240740360000@3228930778>
In-Reply-To: <200710240740360000@3228930778>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200710240856.35227.josh@agliodbs.com>

Magnus,

> Unrelated, we could change the frontpage to only show the first event per
> company. The rest would only be listed on the details page.

That's a great idea!

What about also making the representation of training events more compact? =
=20
Currently we have a fairly space-consumptive layout:

2007-10-22 =E2=80=93 2007-10-26
PostgreSQL Administration Boot Camp
(Morrisville, NC, United States)

2007-11-13 =E2=80=93 2007-11-15
PostgreSQL Database Implementation, Management, and Tuning
(London, United Kingdom)

2007-11-12 =E2=80=93 2007-11-16
Intense PostgreSQL Training (Certification Available)
(Ontario, CA, United States)=20

What if we did:

Upcoming Training

PostgreSQL Administration ... 2007-10-22
PostgreSQL Database Implem ...2007-11-13
Intense PostgreSQL Trainin ...2007-11-12
PostgreSQL Tuning & Perfor ...2007-12-01
etc. ...

With all links actually going to:
http://www.postgresql.org/about/eventarchive#training
(yes, we'd have to create that header link)

That would make the fighting for the "top 3" spot less intense.

=2D-=20
Josh Berkus
PostgreSQL @ Sun
San Francisco