+@ruser{LilyPond command index}:
+an index of all LilyPond @code{\commands}.
+
+@item
+@ruser{LilyPond index}:
+a complete index.
+
+@end itemize
+
+
+@node About the Application Usage (AU)
+@unnumberedsubsec About the Application Usage (AU)
+
+This book explains how to execute the program and how to integrate
+LilyPond notation with other programs.
+
+@itemize
+
+@item
+@rprogram{Install}:
+explains how to install LilyPond (including compilation if
+desired).
+
+@item
+@rprogram{Setup}:
+describes how to configure your computer for optimum LilyPond
+usage, such as using special environments for certain text
+editors.
+
+@item
+@rprogram{Running LilyPond}:
+shows how to run LilyPond and its helper programs. In addition,
+this section explains how to upgrade input files from previous
+versions of LilyPond.
+
+@item
+@rprogram{LilyPond-book}:
+explains the details behind creating documents with in-line music
+examples, like this manual.
+
+@item
+@rprogram{Converting from other formats}:
+explains how to run the conversion programs. These programs are
+supplied with the LilyPond package, and convert a variety of music
+formats to the @code{.ly} format.
+
+@end itemize
+
+
+@node About the Snippet List (SL)
+@unnumberedsubsec About the Snippet List (SL)
+
+@cindex snippets
+@cindex LSR
+
+@ref{Top,LilyPond Snippet List,,lilypond-snippets}: this shows a
+selected set of LilyPond snippets from the
+@uref{http://lsr@/.dsi@/.unimi@/.it,LilyPond Snippet Repository}
+(LSR). All the snippets are in the public domain.
+
+Please note that this document is not an exact subset of LSR. LSR
+is running a stable LilyPond version, so any snippet which
+demonstrates new features of a development version must be added
+separately. These are stored in @file{input/new/} in the LilyPond
+source tree.
+
+The list of snippets for each subsection of the Notation Reference
+(NR) are also linked from the @strong{See also} portion.
+
+
+@node About the Internals Reference (IR)
+@unnumberedsubsec About the Internals Reference (IR)
+
+@ref{Top,Internals Reference,,lilypond-internals}: this is a set
+of heavily cross linked HTML pages which document the nitty-gritty
+details of each and every LilyPond class, object, and function.
+It is produced directly from the formatting definitions in the
+source code.
+
+Almost all formatting functionality that is used internally is
+available directly to the user. For example, most variables that
+control thickness values, distances, etc., can be changed in input
+files. There are a huge number of formatting options, and all of
+them are described in this document. Each section of the Notation
+Reference has a @b{See also} subsection, which refers to the
+generated documentation. In the HTML document, these subsections
+have clickable links.
+
+
+@node Other documentation
+@unnumberedsubsec Other documentation
+
+There are a number of other sources of information which may be
+very valuable.
+
+@itemize
+
+@item News: This is a summary of important changes
+and new features in LilyPond since the previous version.
+
+@item @uref{http://lists.gnu.org/archive/html/lilypond-user/, The
+lilypond-user mailist archives}: this is a collection of previous
+emails sent to the user list. Many questions have been asked
+multiple times; there is a very good chance that if you have a
+question, the answer might be found in these archives.
+
+@item @uref{http://lists.gnu.org/archive/html/lilypond-devel/, The
+lilypond-devel mailist archives}: this is a collection of previous
+emails sent to the developer's list. The discussion here is more
+technical; if you have an advanced question about lilypond
+internals, the answer might be in these archives.
+
+@item Embedded music fragments: in all HTML documents that have
+music fragments embedded, the exact LilyPond input that was used
+to produce that image can be viewed by clicking the image.
+
+@item Init files: The location of the documentation files that are
+mentioned here can vary from system to system. On occasion, this
+manual refers to initialization and example files. Throughout
+this manual, we refer to input files relative to the top-directory
+of the source archive. For example,
+@file{input/@/lsr/@/dirname/@/bla@/.ly} may refer to the file
+@file{lilypond@/2.x.y/@/input/@/lsr/@/dirname/@/bla@/.ly}. On
+binary packages for the UNIX platform, the documentation and
+examples can typically be found somewhere below
+@file{/usr/@/share/@/doc/@/lilypond/}. Initialization files, for
+example @file{scm/@/lily@/.scm}, or
+@file{ly/@/engraver@/-init@/.ly}, are usually found in the
+directory @file{/usr/@/share/@/lilypond/}.
+