>From 59d55b87f1a445471e20d5c2b7e0b0dfc702a5f6 Mon Sep 17 00:00:00 2001 From: Simon Albrecht Date: Sat, 3 Dec 2016 23:00:48 +0100 Subject: [PATCH] Doc CG 6.1: Add caveat on website work --- Documentation/contributor/website-work.itexi | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) diff --git a/Documentation/contributor/website-work.itexi b/Documentation/contributor/website-work.itexi index 588d705..6e858f0 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 the contents of the website to be +up to date 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 address@hidden://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 -- 1.9.1