public inbox for [email protected]  

help / color / mirror / Atom feed

From: Magnus Hagander <[email protected]>
To: Marc G. Fournier <[email protected]>
To: Josh Berkus <[email protected]>
Cc: [email protected]
Subject: Re: Change in policy on News?
Date: Mon, 9 Jan 2006 21:11:48 +0100
Message-ID: <[email protected]> (raw)

> > I'd love this, but it would require a site design change.  If you 
> > remember, we'd talked about dividing the news tickers into 
> 4 parts:  News, Product
> > Announcements, Events and Training.   However, that didn't 
> work with the
> > design for the home page.
> 
> How much work would it be to fix up the right column on the main page?
> 
> Initial thoughts:
> 
>    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

view thread (13+ 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], [email protected]
  Subject: Re: Change in policy on News?
  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