> There is really no reason we should "forget about
> Konqueror"--it's sufficiently
> modern that it should support CSS1 and at least most of
> CSS2, and a fair
> selection of Javascript constructs.  It's possible to
> create a decent site 
> within those constraints, keeping in mind that it doesn't
> have to look
> *identical* on both Konqueror and more recent browsers,
> just "good".
> Graceful degredation in webpages is not rocket science.
> 
> However, one thing that we do need to keep in mind is that
> people who
> haven't yet installed any other graphical environment may
> wish to download
> Trinity packages--in other words, it would be wise to
> create something
> that is usable in text-based browsers like Lynx (it doesn't
> have to be
> elegant, but it should be possible to get from the root
> page to the package
> downloads that way).
> 
> > > Not using databases is a big problem, since it
> practically constrains
> > > you to use static pages.
> > >
> > Basically - why is is this so bad?
> 
> Depends on what we're trying to achieve.  Dynamic
> pages ease certain
> types of collaboration and user-added content, but static
> pages are not
> intrinsically evil and put less of a load on the server.

Please. Please! No JavaScript with the Trinity web site. Supporters of JavaScript should take long walks on short piers, preferably while inebriated.

I hate JavaScript, the bane of the internet. Bandwidth hog and security nightmare.

Bad enough already that I have to white list that crap to access etherpad and the wiki. (Hint, hint.)

Please create static web pages.

Darrell