From owner-freebsd-doc  Sun May 25 14:36:57 1997
Return-Path: <owner-doc>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id OAA10453
          for doc-outgoing; Sun, 25 May 1997 14:36:57 -0700 (PDT)
Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA10447
          for <doc@freebsd.org>; Sun, 25 May 1997 14:36:55 -0700 (PDT)
Received: from localhost (jfieber@localhost)
	by fallout.campusview.indiana.edu (8.8.5/8.8.5) with SMTP id QAA25925
	for <doc@freebsd.org>; Sun, 25 May 1997 16:36:53 -0500 (EST)
Date: Sun, 25 May 1997 16:36:52 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: doc@freebsd.org
Subject: Handbook slicing
Message-ID: <Pine.BSF.3.96.970525161620.18375H-100000@fallout.campusview.indiana.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-doc@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

What do people think about dividing up large document (eg, the
handbook) in to smaller HTML chunks?  I don't much care for how
it is currently done with the handbook--too many nodes that are
too small.

As a test, I've broken things up just at the chapter level which
makes for a lot fewer but larger nodes.  I sort of like it
better but I want some other opinions.  So, point your browser
at:

 http://fallout.campusview.indiana.edu/~jfieber/hb1/BOOK-0001.html

and tell me what you think.  Also, if you can point to examples
of large documents on the web that you think are well done, let
me know.

-john