This site is now updated and looks just as pretty as www.lyx.org.
(still waiting for the update of the main site but my test site looks
pretty anyway -- should be only a couple of minutes)

I think there are only a few minor nitpicks left to clear up:

1. translation_hints.php3 hasn't been converted to clean xhtml yet.
2. the guii table renders with black background in Netscape (boo)
   simple tricks don't seem to be working at present.  Might try again
   later.  It is still readable and actually fairly pleasant for a bug.
2a. Opera doesn't want to "text-align: center;" the guii table status
    entries.
3. I have only checked validity of a few of the pages since only minor
   changes have occurred since last time when they were essentially all
   valid.

More importantly,  _developers listen up_,  the css files,  start.php3 and
end.php3 are _identical_ between both www-user and www-devel.  I'd like to
keep it that way if possible so we can maintain the two sites a bit
easier (any improvement for one can immediately be applied to the other).
The two cvs modules keep their own copies of the files though since we
don't want to loose both sites if one goes belly up.

As a result of this I have shifted the navbar array out into an included
file where it belonged in the first place.  Although it might have been
nice to fully automatically generate the array -- too much like hard work
methinks.  Anyway,  as a result of sharing the css files the menu on
www.devel.lyx.org is bound to be too narrow now since the menus are a few
characters wider in www-devel.  I'm inclinded to control those widths in
separate site-specific css files.  www-devel already has a devel.css just
for the td.guii* settings.

Of course now that this is finished everyone is going to want the blue
bgimage instead of the green one...

Actually there is one interdependence as a result of the identical CSS
files:  www-devel gets its background image from www.lyx.org.  Hmmm...
perhaps another reason for pushing some stuff into site-specific files.
Of course, if netscape obeyed relative URLs in CSS files correctly we
wouldn't have this problem.

Allan. (ARRae)

Reply via email to