| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-www(at)postgresql(dot)org |
| Subject: | Re: Training events policy ... first test case |
| Date: | 2007-10-24 15:56:35 |
| Message-ID: | 200710240856.35227.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
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?
Currently we have a fairly space-consumptive layout:
2007-10-22 – 2007-10-26
PostgreSQL Administration Boot Camp
(Morrisville, NC, United States)
2007-11-13 – 2007-11-15
PostgreSQL Database Implementation, Management, and Tuning
(London, United Kingdom)
2007-11-12 – 2007-11-16
Intense PostgreSQL Training (Certification Available)
(Ontario, CA, United States)
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.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2007-10-24 16:10:19 | Re: Training events policy ... first test case |
| Previous Message | Stefan Kaltenbrunner | 2007-10-24 06:52:04 | Re: Problem with survey code |