>>>>> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes:
Amir> OK. I did a semi-major overhaul of the pages' content and
Amir> linkage. The site (sunsite.auc.dk/lyx) is now "two-tiered". The
Amir> navbar contains links to "Home, News, About, Download, Internet,
Amir> and Devvies", and each of those pages (except News) then has
Amir> links to sub-pages, like the mailing list page, LyX versions,
Amir> screenshots, etc. I changed some of the pages' names, and also
Amir> changed some of their content, but usually not by too much.
It looks very good! I'll try to throw in a couple criticisms for good
measure, however.
In internet.php3, you forgot www.it.lyx.org, hosted by Juergen.
In the platform page, the first paragraph ends with "..., and Solaris,
and Digital Unix. " Is it just me, or is there an extraneous "and"?
Note that Digital Unix (aka DEC OSF/1) is now Tru64 Unix :)
For OS/2, you could give mailto: URLs for SMiyata and Arndt, if they
accept to receive e-mail on this... You could maybe take the first
long paragraph of README.OS2 intead of the e-mail from Arndt, or at
least use cvsweb/checkout to ling to README.OS2 and
INSTALL.OS2. Similarly, the mentions of README and INSTALL for Unices
should be URLs.
Amir> - download.php3 still seems long to me. Should I put, e.g.,
Amir> "stuff with relevance to lyx" on a separate page?
Yes. And maybe setup the list in some sort of table, so that it is
more readable.
Amir> - news.php3 mentions v1.0.3 and links to a CVS checkout of
Amir> CHANGES. While linking to a CVS checkout is Cool, and may even
Amir> be Useful sometimes, here I think it's misleading, because the
Amir> CHANGES file will reflect things that aren't in CHANGES!
You should mention that CHANGES may contain things that are not yet
released.
Amir> - Online docs would definitely be Cool. They should of course be
Amir> HTML, not ps, so that people can look up specific things. And of
Amir> course, now that DocBook is working so well (yay!) they should
Amir> be easy to convert. Right?
Or maybe PDF, if somebody has access to pdflatex or distiller.
Amir> If we did that, I think it would be easy to use PHP to create
Amir> submenus for Download, About, etc. I know Asger said they would
Amir> be hard to maintain, but I think with creative programming, we
Amir> might be able to set it up so that moving files around would
Amir> require changing information in only one place.
Yes, I think each page should have its own submenus in place of the
mailing-lists in the navbar, if possible.
JMarc
