>>>>> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes:

Amir> On Mon, Jul 12, 1999 at 10:34:11AM +0200, Jean-Marc Lasgouttes
Amir> wrote:
>> >>>>> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes:
>> 
>> Small comments:
>> 
>> - in the navbar, the graphical tour should be available

Amir> In fact, you may have noticed that the graphical tour isn't
Amir> available at all! I didn't want to save each page & gif
Amir> separately, then upload them all to sunsite. Can someone send me
Amir> a tgz?

Can't wget do that for you?

Amir> Well, the second part is the archives. Of course, you know
Amir> that. What's the solution, though? We have a page that describes
Amir> all the mailing lists, & we have links to the list archives. Do
Amir> we take the archive links out of the navbar? I think having them
Amir> there just might make some people look there before mailing the
Amir> list for help. We could put the mailing list page link in the
Amir> mailing list section of the navbar... but then what labels would
Amir> we give things so that people know that the first is a page
Amir> describing all the lists, while the other links are just links
Amir> to archives?

The short title could be 'lists archives' instead of 'mailing
lists'. Maybe Devvies should be replaced with Devel, since it is the
name of the list. 

Amir> I agree that the foo.lyx.org mirrors should be listed. (a) I
Amir> don't know them. (b) do we make another navbar section with the
Amir> mirrors, or just have a mirrors page?

Amir> Also, since the phtml won't work, what do we do about feedback?

It could just be implemented as a mailto: url.

Amir> Is the navbar getting too big? We've got 9 things in the navbar,
Amir> lgt would make 10, mirrors 11. Do we want to perhaps break
Amir> things down into About, Download, Main? Then have a separate
Amir> submenu for each, s.t. the navbar shows the main menu, the
Amir> submenu that makes sense in that context, plus the mailing list
Amir> archives & configuration thing? Or is that too complicated.

It could be nice.

JMarc

Reply via email to