Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Mar 2001 22:55:06 +0900
From:      Jun Kuriyama <kuriyama@imgsrc.co.jp>
To:        Nik Clayton <nik@FreeBSD.ORG>
Cc:        doc@FreeBSD.ORG
Subject:   Re: http://www.freebsd.org/docs/, /FAQ/, /handbook/, and others
Message-ID:  <7m7l1jfcqt.wl@waterblue.imgsrc.co.jp>
In-Reply-To: <20010318143907.A13242@canyon.nothing-going-on.org>
References:  <20010314212034.A45244@canyon.nothing-going-on.org> <7mk85rvksr.wl@waterblue.imgsrc.co.jp> <20010315103248.A49019@canyon.nothing-going-on.org> <7mg0gdt0mg.wl@waterblue.imgsrc.co.jp> <20010318143907.A13242@canyon.nothing-going-on.org>

next in thread | previous in thread | raw e-mail | index | archive | help
At 18 Mar 2001 14:40:42 GMT,
nik wrote:
> Currently, 20 in the case of the FAQ, 172 in the case of the Handbook.
> 
> Is that too many?  Personally, I don't think so.

I think that is many, but that's only my point of view...

> I would like the canonical URL for a document to be:
> 
>     http://www.freebsd.org/docs/<lang.encoding>/{books,articles}/document/{index,article,book}.html
> 
> Basically, the result of running 'make install' in the doc/ tree.

As one of Documentation Project team, I think your plan is freindly
for us.  On the other hand, this is not friendly for current www
directory hierarchy.

> Change the way we do things.  Instead of having a CVS repo that looks
> like
> 
>     www/{en,ja,es,...}
> 
> have one that looks like
> 
>     www/{data,cgi,share,...}
> 
> The data/ directory is where all the existing content goes.

It seems that is not good idea.  At doc/ tree, we use separated
directory for each translation project.  We can maintain translated
documents without breaking other translated ones.  At doc/ja* tree, we
plan to use another toolchain to build PostScript version (I think it
is possible on doc package build machine by using another $PREFIX as
you said long long ago...)  And we can use language specific variable
configuration in doc/ja*/*/Makefile.inc now.

Using your plan on www/ tree breaks these features.

> I haven't written any infrastructure to support what I've just described
> yet, but I think it would certainly be an interesting exercise for
> someone to do.  Then we could test it out, and see what problems (if
> any) it causes, and whether or not it really is a benefit.
> 
> Does anyone want to put together a prototype?
...
> Could do.  Patches?

We are talking about *design* of future www structure, not
*implementation* of that.  Implementing before designing carefully
will not make good result.


-- 
Jun Kuriyama <kuriyama@imgsrc.co.jp> // IMG SRC, Inc.
             <kuriyama@FreeBSD.org> // FreeBSD Project

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7m7l1jfcqt.wl>