Hi devels, would please someone push the attached patches to staging?
I've chained them on top of staging (19fa6068cf3a7c5f02c13d5b57be895665da00bf) by cherry-picking them to _one_ branch (not single branches for each patch) and successfully ran make website. Thanks Urs
>From f23a749ea217b4d683a7802c3d764d4c16ab30cb Mon Sep 17 00:00:00 2001 From: Urs Liska <[email protected]> Date: Tue, 7 Jan 2014 12:18:35 +0100 Subject: [PATCH 1/5] Issue 3785: Web:Examples: Enclose in box I think the pages below Introduction (and probably Community too) should consistently start with a box and a subheading, because there is no eye-catching page heading. This is _one_ option to do that for the Examples page. Others would be: - Make that @div only enclose the introductory paragraph - enclose the introductory paragraph _and_ - add a headingless div around the examples _or_ - add a div with @subheading "Gallery" --- Documentation/web/introduction.itexi | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/Documentation/web/introduction.itexi b/Documentation/web/introduction.itexi index 5d2f8c6..1ec99ed 100644 --- a/Documentation/web/introduction.itexi +++ b/Documentation/web/introduction.itexi @@ -296,6 +296,10 @@ already decided to try LilyPond, first read about our @node Examples @unnumberedsec Examples +@divClass{column-center-top} + +@subheading Beautiful examples + LilyPond is a powerful and flexible tool for engraving tasks of all kinds. Please browse our gallery of examples and be inspired! @@ -422,6 +426,7 @@ contributed by Hu Haipeng, a blind composer. @exampleImage{orchestra} @newsEnd +@divEnd @divClass{column-center-bottom} @subheading Where now? -- 1.7.10.4
>From 118023885a557ad8ae177d60ddc00502bb851eb9 Mon Sep 17 00:00:00 2001 From: Urs Liska <[email protected]> Date: Tue, 7 Jan 2014 12:30:54 +0100 Subject: [PATCH 2/5] Issue 3785: Web:Productions: Add title box As stated in https://codereview.appspot.com/48450044/ I think the Introduction pages should have a title box giving the user a first idea about the page. In this case the visitor (currently) would reach the page, doesn't see a heading and is faced two boxes, "Concerts" and "Published sheet music" without further introduction. --- Documentation/web/introduction.itexi | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/Documentation/web/introduction.itexi b/Documentation/web/introduction.itexi index 1ec99ed..bfd02c0 100644 --- a/Documentation/web/introduction.itexi +++ b/Documentation/web/introduction.itexi @@ -573,6 +573,16 @@ try LilyPond, first read about our @ref{Text input}. @node Productions @unnumberedsec Productions +@divClass{column-center-top} + +@subheading Productions using LilyPond + +Here you can read about people who actually use LilyPond +in their productions, be it for performances of their +music or as published scores. + +@divEnd + @divClass{column-left-top} @subheading Concerts -- 1.7.10.4
>From 609db261fa0c644032a0d63514cb296cfeae02f1 Mon Sep 17 00:00:00 2001 From: Urs Liska <[email protected]> Date: Tue, 7 Jan 2014 12:35:32 +0100 Subject: [PATCH 3/5] Issue 3785: Web:Reviews: Add title box Same as https://codereview.appspot.com/38560044/ The Introduction pages should have a "title box" --- Documentation/web/introduction.itexi | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Documentation/web/introduction.itexi b/Documentation/web/introduction.itexi index bfd02c0..189d567 100644 --- a/Documentation/web/introduction.itexi +++ b/Documentation/web/introduction.itexi @@ -731,6 +731,12 @@ If you've already decided to try LilyPond, first read about our @node Reviews @unnumberedsec Reviews +@divClass{column-center-top} +@subheading What do people say about LilyPond? + +@divEnd + + @divClass{column-left-top} @subheading Published articles -- 1.7.10.4
>From d0a1f2145b6c8335d1cbf1f4aa2baade791829d1 Mon Sep 17 00:00:00 2001 From: Urs Liska <[email protected]> Date: Tue, 7 Jan 2014 12:51:02 +0100 Subject: [PATCH 4/5] Issue 3785:Web:Background: Reword intr. paragraph I've always found this page confusing because I didn't understand why there is this "placeholder" page. This commit addresses this by making the "manual" issue explicit. Additionally I consider it more useful to _first_ tell the reader what it is and _then_ advise him to skip the essay instead of _immediately_ telling him "Probably you won't want to read this". If it is necessary to have the link at the end of a paragraph (and not only of a sentence) I'd simply insert a new paragraph after the link. --- Documentation/web/introduction.itexi | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/Documentation/web/introduction.itexi b/Documentation/web/introduction.itexi index 189d567..af0c9f7 100644 --- a/Documentation/web/introduction.itexi +++ b/Documentation/web/introduction.itexi @@ -556,9 +556,11 @@ LilyPond, first read about our @ref{Text input}. We have an extensive essay describing computational aesthetics: the art of creating beauty with a computer. -If you just want a quick introduction to LilyPond, the essay might -be too much material to read. If you would like to read it now, -please progress to @ref{Essay}. +This is interesting reading if you are interested in an in-depth +discussion of our fundamental ideas. Due to its volume the +essay is available as a "manual". If you would like to read +it now, please progress to @ref{Essay}. However, if you just +want a quick introduction to LilyPond, you might skip it for now. @divEnd @divClass{column-center-bottom} -- 1.7.10.4
>From d888f94aeb3a65f42ad6610d3a971d901df31c97 Mon Sep 17 00:00:00 2001 From: Urs Liska <[email protected]> Date: Tue, 7 Jan 2014 12:51:02 +0100 Subject: [PATCH 5/5] Issue 3785:Web:Introduction: Reword "Our Goal" box The content of this box was somewhat confusing and inconsistent. See http://lists.gnu.org/archive/html/lilypond-devel/2014-01/msg00011.html This commit tries to incorporate the suggestions made in this thread as far as I considered appropriate. --- Documentation/web/introduction.itexi | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/Documentation/web/introduction.itexi b/Documentation/web/introduction.itexi index af0c9f7..9e7265c 100644 --- a/Documentation/web/introduction.itexi +++ b/Documentation/web/introduction.itexi @@ -20,10 +20,14 @@ soulless look of computer-printed sheet music. Musicians prefer reading beautiful music, so why couldn't programmers write software to produce elegant printed parts? -The result is a system which frees musicians from the details of -layout, allowing them to focus on making music. LilyPond works -with them to create publication-quality parts, crafted in the best -traditions of classical music engraving. +The result is a program that creates beautiful sheet music +following the best traditions of classical music engraving. +It takes care of the details of layout programmatically, +allowing composers, transcribers and publishers to focus +on the @emph{music} instead of improving their software's +default output. Performers will get parts that let them +concentrate on @emph{playing} music instead of @emph{reading} it. + @divEnd -- 1.7.10.4
_______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
