APA> I'd like to get some feedback from people surfing APA> http://xemacs.sourceforge.net/ APA> So far I have NONE. Vin> 1. Clicking on the "Mailing List Archives" link yielded: Vin> The requested URL /Lists/Archive/index.cgi was not found on Vin> this server. Yes, this is not done at all. Vin> Similarly, following the link to "Join the xemacs-beta mailing Vin> list" yielded: Vin> The requested URL /Lists/index.html was not found on this Vin> server. Vin> It looks like all of the /Lists links are dead. Yep. Vin> 2. I notice the footers all claim to be part of http://www.xemacs.org Vin> (and indeed points there), but that's not really correct. I'm Vin> confused about this because the link at the top left of every page Vin> says www.xemacs.org, but it points to sourceforge. Yes. We're currently sitting between the chairs. I am concerned that using <base href="http://www.xemacs.org/"> in template.html (all page contents get wrapped into this template) is more a curse than a blessing. I have changed it to <base href="http://xemacs.sourceforge.net/"> for the sourceforge site. AFAIK, "base href" is a feature to be used when web documents are sent off via e-mail, to provide a base for all relative links. Using this feature as a means of website design is an error, I believe. It is the cause for all the broken links in "Architecting XEmacs". All local links in these documents are suddenly taken to be relative to <base href="http://xemacs.sourceforge.net/"> not to http://xemacs.sourceforge.net/Architecting XEmacs Throwing out <base href="http://xemacs.sourceforge.net/"> is a tedious task, which perl would probably do for me. I would like to get some feedback from yall, especially the ones who decided to use <base href="http://xemacs.sourceforge.net/"> What was the motivation? Best regards, Adrian Vin> 3. It looks like all of the links on Architecting XEmacs are dead. Vin> Thanks for doing this, Adrian. Vin> - vin