From owner-freebsd-doc Thu Mar 1 6:57:49 2001 Delivered-To: freebsd-doc@freebsd.org Received: from nothing-going-on.demon.co.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id 59A7837B719 for ; Thu, 1 Mar 2001 06:57:44 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.1/8.11.1) id f21EuNN03264; Thu, 1 Mar 2001 14:56:23 GMT (envelope-from nik) Date: Thu, 1 Mar 2001 14:56:23 +0000 From: Nik Clayton To: Jun Kuriyama Cc: doc@FreeBSD.org Subject: Re: cvs commit: www/en Makefile Message-ID: <20010301145623.A3225@canyon.nothing-going-on.org> References: <200102241031.f1OAVTZ82598@freefall.freebsd.org> <20010225064044.A68105@canyon.nothing-going-on.org> <20010227122027.A2079@paula.panke.de.freebsd.org> <7mwva9y48r.wl@waterblue.imgsrc.co.jp> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="9amGYk9869ThD9tj" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <7mwva9y48r.wl@waterblue.imgsrc.co.jp>; from kuriyama@imgsrc.co.jp on Thu, Mar 01, 2001 at 11:04:52PM +0900 Organization: FreeBSD Project Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 01, 2001 at 11:04:52PM +0900, Jun Kuriyama wrote: > At Tue, 27 Feb 2001 12:20:27 +0100, > Wolfram Schneider wrote: > > This is confusing and not acceptable. A page which can > > be read on a web server will be read (Murphys Law). This will > > increase the robots load by several ten-thousend page views per day! > > In general, never use symlinks to directories on a web server. >=20 > I support Wolfram about this. We should avoid symlinks as much as we > can. This breaks search engine's result by returning same contents > with multiple URLs. Way, way, way too late: http://www.freebsd.org/news/ http://www.freebsd.org/news/index.html http://www.freebsd.org/news/news.html and other examples (commercial/, copyright/, docproj/, gallery/, internal/, projects/, search/, security/). I'd like to=20 1. Agree that all documentation installs in the website under a single point. Currently, I prefer docs/ (or doc/). 2. Use symlinks to grandfather in existing shortcuts (/FAQ, /handbook, and a handful of others) so that existing URLs work. Then our mirrors can be true mirrors, without having to see our httpd.conf (or even run the same server software that we do). 3. Establish a policy that no new documentation should install=20 directly under the document root. Much, much, much longer term I'd like to consider moving the documentation= =20 off on to its own subdomain, doc.freebsd.org or similar. That's a sufficiently big project that I don't want to go anywhere near it at the moment, as we'd just get bogged down. > We now have good consistency for layout of documents and translated > ones. We can get English Handbook via /handbook/ and Japanese Handbook > via /ja/handbook/. Is that appropriate for the foreign languages? On the Japanese web site shouldn't /handbook/ default to the Japanese Handbook? I don't know the answer to this question. I can see the point in having the same URLs go to identical content on the different language web sites. But it also makes sense that some URLs are just shortcuts, that select a particular default. And that on the translated web sites, the defaults should be for the content in the local language. I'd be interested to hear what others think. > Problems like web server's load can be solved easily by upgrading > machine for web server. But we should avoid beginner's confusion > which may be caused by "same contents which can be refered by multiple > URLs". The HTML is hypertext and why can we point *one* contents with > HTML anthor from another place? Is placing same copy (of course, it's > copy from user's point of view) with multiple URLs. >=20 > Comments? Per 1, 2, and 3 above. The idea is that all documents move under a common namespace on the webserver. Old URLs continue to be supported, but we don't introduce any new URLs like that (so, for example, http://www.freebsd.org/design-44bsd/ should never, ever be working URL). We should also periodically monitor the error logs, as people learn and bookmark the new URLs. Suppose that, right now, .../FAQ/ gets 10,000 hits a month (I've got no idea what the true figure is). Eventually that'll drop, as the new URLs become commonplace. We could agree that when the figure drops to something like 50 hits a month (which could take a year or more) we replace .../FAQ/ with a message that says "This content has moved to...". I am *not* talking about an overnight change. N --9amGYk9869ThD9tj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjqeYxYACgkQk6gHZCw343X12gCeOVgco1UHC7AiSkm3sP3AAyYf Wz8AnAxeVUeGxyO1UpfPmNs5bcNWhaVd =DaDL -----END PGP SIGNATURE----- --9amGYk9869ThD9tj-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message