Web: home page: add examples/images, reduce news to headlines

Web: home page: add examples/images, reduce news to headlines

Examples/images is moved from the Introduction section to the
home page.

[pwm, 2016-08-29 21:49:41]

Please review and let me know what you think about these changes.  They are
inspired by recent and not so recent discussions on the lists.  

Here's a screenshot of the home page with these changes:
https://drive.google.com/open?id=0ByNTIEA63_a_bkxrWlpKcW43cHc

The images and other content from the 'Examples' page is moved to the home page,
and the 'Examples' page is removed from the 'Introduction' section.

The news entries on the home page are reduced to just headline links in the
sidebar.  They link to the 'Old News' page where the full entries live (under
'Community').  And that page is renamed to just 'News'.

(I tried to make the headline links point to individual entries on the News
page, but the texinfo @anchor tag is unrecognized by our build scripts.  So an
upgrade is needed before we can use this feature.)

If these changes are to land as they are (pending review and discussion) then we
may want to add redirects to the htaccess file for two changed urls before
landing them:

old-news.html -> news.html
examples.html -> home page

-Paul

[fedelogy, 2016-08-30 15:07:47]

On 2016/08/29 21:49:41, pwm wrote:
> 
> The images and other content from the 'Examples' page is moved to the home
page,
> and the 'Examples' page is removed from the 'Introduction' section.
> 

Paul, thanks for tackling this issue!

I'd prefer a slider of images to save vertical space and scrolling.
Some time ago I made a quick test of a pure CSS image slider of lilypond
examples, but never tried to apply it on texinfo and lilypond source.

I _guess_ that the problem with the @anchor tag is due to
lilypond-texi2html.init

[pwm, 2016-08-30 20:02:14]

All 'Old news' -> 'News' & rearrange examples

[pwm, 2016-08-30 20:51:37]

On 2016/08/30 15:07:47, fedelogy wrote:
> 
> Paul, thanks for tackling this issue!

Thanks, glad to help.  It's been on my wish list for awhile.

> I'd prefer a slider of images to save vertical space and scrolling.
> Some time ago I made a quick test of a pure CSS image slider of lilypond
> examples, but never tried to apply it on texinfo and lilypond source.

Hmmm, I don't mind the scrolling or use of vertical space, and I like how
the basic page of images fits the simple aesthetic of the rest of the site.
Would a slider work well with the various heights of the images?  Maybe it's
something we could consider for a future revision?

> I _guess_ that the problem with the @anchor tag is due to
> lilypond-texi2html.init

Probably so.  Maybe @anchor is a newer feature in texinfo?

I've uploaded a patch set 2 that succeeds at a full 'make doc' and adds
a second commit:

Web: Rearrange examples/images on home page

To raise the prominence of some common use cases,
the 4 marked with an asterisk (*) below.

NEW ORDER:
Classical Music
Complex Notation
Early Music
Modern Music
* Tablature
* Vocal Music
* Popular Music
Efficient, flexible creation of performance materials
* Educational Applications
Schenker Graphs
Customized Output
Large Projects

OLD ORDER:
Classical Music
Complex Notation
Early Music
Modern Music
Efficient, flexible creation of performance materials
Tablature
Schenker Graphs
Customized Output
Vocal Music
Educational Applications
Popular Music
Large Projects

[dak, 2016-08-30 21:52:47]

paulwmorris@gmail.com writes:

> On 2016/08/30 15:07:47, fedelogy wrote:
>
>> Paul, thanks for tackling this issue!
>
> Thanks, glad to help.  It's been on my wish list for awhile.
>
>> I'd prefer a slider of images to save vertical space and scrolling.
>> Some time ago I made a quick test of a pure CSS image slider of
> lilypond
>> examples, but never tried to apply it on texinfo and lilypond source.
>
> Hmmm, I don't mind the scrolling or use of vertical space, and I like
> how the basic page of images fits the simple aesthetic of the rest of
> the site.

There is navigation and language selection at the bottom of the page.
Having to scroll all the way down to get at it is not good when the
material in the middle is not what you are after.  If you want to have
vertical excess, this material has to be moved to a place on the top
portion.

> https://codereview.appspot.com/306350043/

-- 
David Kastrup

[Carl, 2016-08-30 22:05:11]

I'm not comfortable with the really long, scrolling, home page.

I think we should make the home page so that it is basically a one-screen page
on a "typical" computer display, and have the full example page be a link titled
"more" or something like that.

Carl

[paul_paulwmorris.com, 2016-08-31 15:39:03]

On 08/30/2016 06:05 PM, Carl.D.Sorensen@gmail.com wrote:

> I'm not comfortable with the really long, scrolling, home page.

Ok, given these concerns that Carl and David raised, let me think some 
more and see what I can come up with.

Maybe just a single example, followed by a list of the other kinds of 
examples, to show the range of what LilyPond can do, with a link to the 
full example page.  (This is another place where @anchor would come in 
handy -- we could link the list items directly to the examples, 
"Tablature" to the tablature example etc.)

Later, if we wanted, we could turn that single example into a CSS slider 
/ slide show type thing where the user could click through some of the 
examples in-place on the home page, as Federico suggests.

Anyway, just some thoughts.  It may be some days before I get back to 
working on this.

-Paul

[ul_openlilylib.org, 2016-09-01 05:18:37]

Am 31. August 2016 16:11:14 MESZ, schrieb Paul <paul@paulwmorris.com>:
>On 08/30/2016 06:05 PM, Carl.D.Sorensen@gmail.com wrote:
>
>> I'm not comfortable with the really long, scrolling, home page.
>
>Ok, given these concerns that Carl and David raised, let me think some 
>more and see what I can come up with.
>
>Maybe just a single example, followed by a list of the other kinds of 
>examples, to show the range of what LilyPond can do, with a link to the
>
>full example page.  (This is another place where @anchor would come in 
>handy -- we could link the list items directly to the examples, 
>"Tablature" to the tablature example etc.)
>
>Later, if we wanted, we could turn that single example into a CSS
>slider 
>/ slide show type thing where the user could click through some of the 
>examples in-place on the home page, as Federico suggests.
>

An option that seems quite natural to display these examples would be the
"accordion" (http://www.w3schools.com/howto/howto_js_accordion.asp).

Urs

>Anyway, just some thoughts.  It may be some days before I get back to 
>working on this.
>
>-Paul
>
>_______________________________________________
>lilypond-devel mailing list
>lilypond-devel@gnu.org
>https://lists.gnu.org/mailman/listinfo/lilypond-devel

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

[pwm, 2016-09-06 15:13:52]

One example on homepage with anchor links

[pwm, 2016-09-06 15:49:43]

Patch set 3 uploaded, with just one example image on the home page and a list of
links to the other examples on the examples page.  I like how this gets an image
of sheet music onto the home page and helps communicate the wide range of
LilyPond's use cases.

Screenshot:
https://drive.google.com/open?id=0ByNTIEA63_a_ZzMtNTFiZHFqN2c

The news links and examples links now link directly to their individual news
item or example.  I realized that the anchor tags (<a>) already exist in the
generated HTML for headings, so it's just a matter of using them.  

(I figured out how to use them for the website.  I consulted the texinfo manuals
but could not find a way to make these kinds of links work for other output
formats.  I assume that when we have support for @anchor it would work.)

(While an interactive accordion or slide-show would be nice, it would be more
work than I can take on at this point.)

-Paul

[ul_openlilylib.org, 2016-09-06 16:09:50]

Am 06.09.2016 um 17:49 schrieb paulwmorris@gmail.com:
> Patch set 3 uploaded, with just one example image on the home page and a
> list of links to the other examples on the examples page.  I like how
> this gets an image of sheet music onto the home page and helps
> communicate the wide range of LilyPond's use cases.
>
> Screenshot:
> https://drive.google.com/open?id=0ByNTIEA63_a_ZzMtNTFiZHFqN2c
>
> The news links and examples links now link directly to their individual
> news item or example.  I realized that the anchor tags (<a>) already
> exist in the generated HTML for headings, so it's just a matter of using
> them.
>
> (I figured out how to use them for the website.  I consulted the texinfo
> manuals but could not find a way to make these kinds of links work for
> other output formats.  I assume that when we have support for @anchor it
> would work.)
>
> (While an interactive accordion or slide-show would be nice, it would be
> more work than I can take on at this point.)

Yes!
I think this is a very nice compromise, just having one image on the
front page (and of course having to decide which one ...) but still
having the others one “encouraging“ click away.

Urs

>
> -Paul
>
> https://codereview.appspot.com/306350043/

[Carl, 2016-09-06 16:39:22]

On 2016/09/06 15:49:43, pwm wrote:

> Screenshot:
> https://drive.google.com/open?id=0ByNTIEA63_a_ZzMtNTFiZHFqN2c
> 

I have not built and tested the webpage, but I think this is exactly the way to
go.  Show an example, and let the user select any other examples they find
interesting.  

I think the only thing remaining is to get the best possible example for the
front page.


Thanks,

Carl

[simon.albrecht, 2016-09-06 19:47:57]

My 2cts.

https://codereview.appspot.com/306350043/diff/40001/Documentation/web.texi
File Documentation/web.texi (right):

https://codereview.appspot.com/306350043/diff/40001/Documentation/web.texi#ne...
Documentation/web.texi:142: @exampleImage{bach-bwv610}
I agree that we should look for the best possible showcase here. I’m not quite
convinced of this one, though that may be due to my difficult relationship with
the church musician cliché :-)

https://codereview.appspot.com/306350043/diff/40001/Documentation/web.texi#ne...
Documentation/web.texi:148: all kinds, including classical music (like this
organ work by J.S.
‘tasks of all kinds, including’
To me this sounds too much like you get a dropdown menu with the following
options :-)
I’d rather have
‘tasks of all kinds, for example’

[pwm, 2016-09-08 03:28:49]

Thanks for the feedback everyone!

On 2016/09/06 16:39:22, Carl wrote:
> 
> I think the only thing remaining is to get the best possible example for the
> front page.

Any suggestions anyone?  I'm fine with the Bach one or whatever people think is
best.  One of the existing ones would be simplest of course.

Simon, I'm fine with your suggestion of "tasks of all kinds, for example" and
will make that change before this lands.  (I'll forego another patch review for
it though, unless anyone objects.)

-Paul

[mail_philholmes.net, 2016-09-08 08:12:12]

----- Original Message ----- 
From: <paulwmorris@gmail.com>
To: <fedelogy@gmail.com>; <dak@gnu.org>; <carl.d.sorensen@gmail.com>; 
<paul@paulwmorris.com>; <ul@openlilylib.org>; <simon.albrecht@mail.de>
Cc: <reply@codereview-hr.appspotmail.com>; <lilypond-devel@gnu.org>
Sent: Thursday, September 08, 2016 4:28 AM
Subject: Re: Web: home page: add examples/images, reduce news to 
headlines(issue 306350043 by paulwmorris@gmail.com)


> Thanks for the feedback everyone!
>
> On 2016/09/06 16:39:22, Carl wrote:
>
>> I think the only thing remaining is to get the best possible example
> for the
>> front page.
>
> Any suggestions anyone?  I'm fine with the Bach one or whatever people
> think is best.  One of the existing ones would be simplest of course.


I think that, of our current examples, the Bach one is best as a general 
illustration.

--
Phil Holmes 

[Carl, 2016-09-08 16:53:49]

On 2016/09/08 03:28:49, pwm wrote:
> Thanks for the feedback everyone!
> 
> On 2016/09/06 16:39:22, Carl wrote:
> > 
> > I think the only thing remaining is to get the best possible example for the
> > front page.
> 
> Any suggestions anyone?  I'm fine with the Bach one or whatever people think
is
> best.  One of the existing ones would be simplest of course.

How about the BWV 861 example from the essay?

http://lilypond.org/doc/v2.18/Documentation/essay/engraved-examples-_0028bwv-...

It shows fewer features (e.g. instrument names, score title) but shows a
beautiful and complex score.

Carl

[paul_paulwmorris.com, 2016-09-13 00:25:23]

On 09/08/2016 12:53 PM, Carl.D.Sorensen@gmail.com wrote:

> How about the BWV 861 example from the essay?
>
>
http://lilypond.org/doc/v2.18/Documentation/essay/engraved-examples-_0028bwv-...

>
>
> It shows fewer features (e.g. instrument names, score title) but shows a
> beautiful and complex score.

That seems fine to me.

Carl, would you like me to hold off on pushing my patch until we sort 
out the example image, or is it ok with you to go ahead and push now and 
do a different example in a follow-up patch?

Last night I tried to get the BWV 861 example to work, without any 
luck.  I made a ly file for it in the Documentation/ly-examples 
directory, but I couldn't get the build scripts to make the images from 
it.  With the ly file in that directory and putting references to the 
example/image into the home page and the examples page, I would just get 
broken links to a non-existing image, even after running a fresh make, 
make website, and make doc.

Does anyone know what's needed?  How to get the build scripts to see my 
file and create the example image?

Thanks,
-Paul

[mail_philholmes.net, 2016-09-13 08:28:48]

----- Original Message ----- 
From: "Paul" <paul@paulwmorris.com>
To: <paulwmorris@gmail.com>; <fedelogy@gmail.com>; <dak@gnu.org>; 
<carl.d.sorensen@gmail.com>; <ul@openlilylib.org>; <simon.albrecht@mail.de>; 
<mail@philholmes.net>; <lilypond-devel@gnu.org>; 
<reply@codereview-hr.appspotmail.com>
Sent: Tuesday, September 13, 2016 1:25 AM
Subject: Re: Web: home page: add examples/images, reduce news to headlines 
(issue 306350043 by paulwmorris@gmail.com)


> On 09/08/2016 12:53 PM, Carl.D.Sorensen@gmail.com wrote:
>
>> How about the BWV 861 example from the essay?
>>
>>
http://lilypond.org/doc/v2.18/Documentation/essay/engraved-examples-_0028bwv-...
>>
>> It shows fewer features (e.g. instrument names, score title) but shows a
>> beautiful and complex score.
>
> That seems fine to me.
>
> Carl, would you like me to hold off on pushing my patch until we sort out 
> the example image, or is it ok with you to go ahead and push now and do a 
> different example in a follow-up patch?
>
> Last night I tried to get the BWV 861 example to work, without any luck. 
> I made a ly file for it in the Documentation/ly-examples directory, but I 
> couldn't get the build scripts to make the images from it.  With the ly 
> file in that directory and putting references to the example/image into 
> the home page and the examples page, I would just get broken links to a 
> non-existing image, even after running a fresh make, make website, and 
> make doc.
>
> Does anyone know what's needed?  How to get the build scripts to see my 
> file and create the example image?
>
> Thanks,
> -Paul
>

I know understanding how images are used is a bit of a problem - which I 
might have understood once, but have now forgotten.  Is the information at 
http://lilypond.org/doc/v2.19/Documentation/contributor/other-repositories 
and http://lilypond.org/doc/v2.19/Documentation/contributor/website-build 
any help?

--
Phil Holmes 

[paul_paulwmorris.com, 2016-09-13 13:26:39]

On 09/13/2016 04:28 AM, Phil Holmes wrote:

> I know understanding how images are used is a bit of a problem - which 
> I might have understood once, but have now forgotten.  Is the 
> information at 
> http://lilypond.org/doc/v2.19/Documentation/contributor/other-repositories 
> and 
> http://lilypond.org/doc/v2.19/Documentation/contributor/website-build 
> any help?

Thanks, those are helpful.  I'll have to remember that those build 
system notes are down there.  I see now that LilyPond is being run on 
the new file and the pdf and png files do end up in:

build/Documentation/ly-examples/out-www

but for some reason those files are not being copied into

build/out-website/website/ly-examples

Where they need to be for the website.

Also, there's another issue.  The scripts to create these example images 
(at two sizes to allow "click to enlarge") use -dpreview so only the 
first system of this bwv861 example makes it into the image.  (sigh)  So 
maybe trying to use this examples machinery is not helpful.  (Unless we 
want to edit all of the examples ly files so that they only output the 
content that should be in the images and then drop the -dpreview.)

At this point it would probably be simplest to just inline the lilypond 
code for this example on the home page, like it is done in the essay.  
(Probably putting it in an include file to avoid duplication.)  We 
wouldn't get "click to enlarge" that way (which was the point of using 
the examples mechanisms) but maybe that's not needed on the home page 
and/or could be a future enhancement.

-Paul

[mail_philholmes.net, 2016-09-13 13:53:13]

----- Original Message ----- 
From: "Paul" <paul@paulwmorris.com>
To: "Phil Holmes" <mail@philholmes.net>; <paulwmorris@gmail.com>; 
<lilypond-devel@gnu.org>; <reply@codereview-hr.appspotmail.com>
Sent: Tuesday, September 13, 2016 2:26 PM
Subject: Re: Web: home page: add examples/images, reduce news to headlines 
(issue 306350043 by paulwmorris@gmail.com)


> On 09/13/2016 04:28 AM, Phil Holmes wrote:
>
>> I know understanding how images are used is a bit of a problem - which I 
>> might have understood once, but have now forgotten.  Is the information 
>> at 
>> http://lilypond.org/doc/v2.19/Documentation/contributor/other-repositories 
>> and http://lilypond.org/doc/v2.19/Documentation/contributor/website-build 
>> any help?
>
> Thanks, those are helpful.  I'll have to remember that those build system 
> notes are down there.  I see now that LilyPond is being run on the new 
> file and the pdf and png files do end up in:
>
> build/Documentation/ly-examples/out-www
>
> but for some reason those files are not being copied into
>
> build/out-website/website/ly-examples
>
> Where they need to be for the website.
>
> Also, there's another issue.  The scripts to create these example images 
> (at two sizes to allow "click to enlarge") use -dpreview so only the first 
> system of this bwv861 example makes it into the image.  (sigh)  So maybe 
> trying to use this examples machinery is not helpful.  (Unless we want to 
> edit all of the examples ly files so that they only output the content 
> that should be in the images and then drop the -dpreview.)
>
> At this point it would probably be simplest to just inline the lilypond 
> code for this example on the home page, like it is done in the essay. 
> (Probably putting it in an include file to avoid duplication.)  We 
> wouldn't get "click to enlarge" that way (which was the point of using the 
> examples mechanisms) but maybe that's not needed on the home page and/or 
> could be a future enhancement.
>
> -Paul


I don't think you can do that.  The reason for all the odd stuff with the 
image files is that the server we host lilypond on does not use lilypond to 
make the website - so all images must be pre-created to allow the website 
itself to be remade.  Note that much of the website it really made using 
make doc during a Gub run, but some of it (the homepage and the \web stuff) 
is made with make website and requires no upload.  The server has cron jobs 
that pull git and run make website.

--
Phil Holmes 

[mail_philholmes.net, 2016-09-13 14:02:23]

----- Original Message ----- 
From: "Paul" <paul@paulwmorris.com>
To: "Phil Holmes" <mail@philholmes.net>; <paulwmorris@gmail.com>; 
<lilypond-devel@gnu.org>; <reply@codereview-hr.appspotmail.com>
Sent: Tuesday, September 13, 2016 2:26 PM
Subject: Re: Web: home page: add examples/images, reduce news to headlines 
(issue 306350043 by paulwmorris@gmail.com)


> On 09/13/2016 04:28 AM, Phil Holmes wrote:
>
>> I know understanding how images are used is a bit of a problem - which I 
>> might have understood once, but have now forgotten.  Is the information 
>> at 
>> http://lilypond.org/doc/v2.19/Documentation/contributor/other-repositories 
>> and http://lilypond.org/doc/v2.19/Documentation/contributor/website-build 
>> any help?
>
> Thanks, those are helpful.  I'll have to remember that those build system 
> notes are down there.  I see now that LilyPond is being run on the new 
> file and the pdf and png files do end up in:
>
> build/Documentation/ly-examples/out-www
>
> but for some reason those files are not being copied into
>
> build/out-website/website/ly-examples

Just thinking about this bit some more - are you running make doc to create 
the images and make website after that?

--
Phil Holmes 

[paul_paulwmorris.com, 2016-09-13 14:41:45]

On 09/13/2016 10:02 AM, Phil Holmes wrote:

> Just thinking about this bit some more - are you running make doc to 
> create the images and make website after that?

Yes, at first after reading those docs you linked to, I thought maybe 
I'd run:

make
make website
make doc

(out of order) but then I ran

make website

got same result, and then

make doc
make website

and same result.

-Paul

[paul_paulwmorris.com, 2016-09-13 14:42:15]

On 09/13/2016 09:52 AM, Phil Holmes wrote:

>> At this point it would probably be simplest to just inline the 
>> lilypond code for this example on the home page, like it is done in 
>> the essay. (Probably putting it in an include file to avoid 
>> duplication.)  We wouldn't get "click to enlarge" that way (which was 
>> the point of using the examples mechanisms) but maybe that's not 
>> needed on the home page and/or could be a future enhancement.
>
> I don't think you can do that.  The reason for all the odd stuff with 
> the image files is that the server we host lilypond on does not use 
> lilypond to make the website - so all images must be pre-created to 
> allow the website itself to be remade.  Note that much of the website 
> it really made using make doc during a Gub run, but some of it (the 
> homepage and the \web stuff) is made with make website and requires no 
> upload.  The server has cron jobs that pull git and run make website.

Ah, ok...  hmm...  so it sounds like we would need to do this home page 
example like the other website images then.  (Assuming we're not using 
the examples scripts because of the -dpreview issue.)

-Paul

[mail_philholmes.net, 2016-09-13 15:19:22]

----- Original Message ----- 
From: "Paul" <paul@paulwmorris.com>
To: "Phil Holmes" <mail@philholmes.net>; <paulwmorris@gmail.com>; 
<lilypond-devel@gnu.org>; <reply@codereview-hr.appspotmail.com>
Sent: Tuesday, September 13, 2016 3:11 PM
Subject: Re: Web: home page: add examples/images, reduce news to headlines 
(issue 306350043 by paulwmorris@gmail.com)


> On 09/13/2016 09:52 AM, Phil Holmes wrote:
>
>>> At this point it would probably be simplest to just inline the lilypond 
>>> code for this example on the home page, like it is done in the essay. 
>>> (Probably putting it in an include file to avoid duplication.)  We 
>>> wouldn't get "click to enlarge" that way (which was the point of using 
>>> the examples mechanisms) but maybe that's not needed on the home page 
>>> and/or could be a future enhancement.
>>
>> I don't think you can do that.  The reason for all the odd stuff with the 
>> image files is that the server we host lilypond on does not use lilypond 
>> to make the website - so all images must be pre-created to allow the 
>> website itself to be remade.  Note that much of the website it really 
>> made using make doc during a Gub run, but some of it (the homepage and 
>> the \web stuff) is made with make website and requires no upload.  The 
>> server has cron jobs that pull git and run make website.
>
> Ah, ok...  hmm...  so it sounds like we would need to do this home page 
> example like the other website images then.  (Assuming we're not using the 
> examples scripts because of the -dpreview issue.)
>
> -Paul
>

Agreed.  I think that what is necessary is to generate the pictures locally, 
put them in Documentation/pictures and also probably push them to 
gperciva/lilypond-extra - they would then work in the same way as the 
pictures in http://lilypond.org/website/windows.html, for example.

--
Phil Holmes

[pwm, 2016-09-15 00:43:03]

Use Bach BWV861 example from essay

[pwm, 2016-09-15 00:51:08]

Now using the Bach BWV861 example from the essay.  Screenshot:
https://drive.google.com/open?id=0ByNTIEA63_a_ZGZrZzlkSUhJeU0

I like the cleaner look since this image doesn't have any title, text, etc. like
the previous one.  If you click on the image you can see a larger version.  I
will upload the pngs to gperciva/lilypond-extra 

-Paul

[ul_openlilylib.org, 2016-09-15 04:42:19]

Am 15.09.2016 um 02:51 schrieb paulwmorris@gmail.com:
> Now using the Bach BWV861 example from the essay.  Screenshot:
> https://drive.google.com/open?id=0ByNTIEA63_a_ZGZrZzlkSUhJeU0
>
> I like the cleaner look since this image doesn't have any title, text,
> etc. like the previous one.  If you click on the image you can see a
> larger version.  I will upload the pngs to gperciva/lilypond-extra
>

I like that solution.

One question: Is that example done without any tweaks? I think so but
want to make sure. If it is it would be worth a mention on the front
page about "automatic engraving", which is one of the main points for
using LilyPond.

Urs


> -Paul
>
>
> https://codereview.appspot.com/306350043/

[pwm, 2016-09-16 16:32:23]

Remove image and ly files from patch

[trevorbaca_gmail.com, 2016-10-03 20:46:15]

On Wed, Sep 14, 2016 at 11:42 PM, Urs Liska <ul@openlilylib.org> wrote:

>
>
> Am 15.09.2016 um 02:51 schrieb paulwmorris@gmail.com:
> > Now using the Bach BWV861 example from the essay.  Screenshot:
> > https://drive.google.com/open?id=0ByNTIEA63_a_ZGZrZzlkSUhJeU0
> >
> > I like the cleaner look since this image doesn't have any title, text,
> > etc. like the previous one.  If you click on the image you can see a
> > larger version.  I will upload the pngs to gperciva/lilypond-extra
> >
>
> I like that solution.
>
> One question: Is that example done without any tweaks? I think so but
> want to make sure. If it is it would be worth a mention on the front
> page about "automatic engraving", which is one of the main points for
> using LilyPond.


The newer, cleaner homepage is a great improvement.

Was lovely to see beautiful engraving straightaway this morning on going to
the site!


Trevor.

-- 
Trevor Bača
www.trevorbaca.com
soundcloud.com/trevorbaca