public inbox for [email protected]
help / color / mirror / Atom feedFrom: Marc G. Fournier <[email protected]>
To: Josh Berkus <[email protected]>
To: [email protected]
Subject: Re: Training events policy ... first test case
Date: Wed, 24 Oct 2007 13:10:19 -0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <200710240740360000@3228930778>
<[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- --On Wednesday, October 24, 2007 08:56:35 -0700 Josh Berkus <[email protected]>
wrote:
> 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. ...
I think you need *at least* Country in there somewhere, if not State/Province
... ppl outside the US, for instance, might grow tired of clicking through if
the result is always something in the US, when all that really interests them
are stuff in the UK ...
- ----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . [email protected] MSN . [email protected]
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
iD8DBQFHH25r4QvfyHIvDvMRAomHAKDCuJ703FhNsSjq7x9bNwLe8qQThQCfSJ2K
3wA2mTYX9lYLh6BneOt9yXY=
=B5WP
-----END PGP SIGNATURE-----
view thread (76+ 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]
Subject: Re: Training events policy ... first test case
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