From: Simon Albrecht <sincero@my.mail.de>
Date: Mon, 5 Dec 2016 07:44:07 +0000 (-0800)
Subject: Doc CG 6.1: Add caveat about website work
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=cc06dbd922171e5242115178f0895e4c8a2c00eb;p=lilypond.git

Doc CG 6.1: Add caveat about website work
---

diff --git a/Documentation/contributor/website-work.itexi b/Documentation/contributor/website-work.itexi
index 588d705f1b..be4cd26f21 100644
--- a/Documentation/contributor/website-work.itexi
+++ b/Documentation/contributor/website-work.itexi
@@ -14,8 +14,25 @@
 @section Introduction to website work
 
 The website is @emph{not} written directly in HTML;
-instead, the source is Texinfo, which is then generated into HTML,
-PDF, and Info formats.  The sources are
+instead it is autogenerated along with the documentation through a
+sophisticated setup, using Texinfo source files.  Texinfo is the
+standard for documentation of GNU software and allows generating
+output in HTML, PDF, and Info formats, which drastically reduces
+maintenance effort and ensures that the website content is
+consistent with the rest of the documentation.  This makes the
+environment for improving the website rather different from common
+web development.
+
+If you have not contributed to LilyPond before, a good starting
+point might be incremental changes to the CSS file, to be found at
+@uref{http://lilypond.org/css/lilypond-website.css} or in the
+LilyPond source code at @file{./Documentation/css/lilypond-website.css}.
+
+Large scale structural changes tend to require familiarity with
+the project in general, a track record in working on LilyPond
+documentation as well as a prospect of long-term commitment.
+
+The Texinfo source file for generating HTML are to be found in
 
 @example
 Documentation/web.texi