Many thanks for creating this site, Jean! The new Wiki is very useful. I would like to echo Luca’s suggestion (below) regarding the presentation of content within pages of the Wiki.
I agree with Luca that the following order — 1. explanatory text 2. beautiful output 3. beautiful code — would be more useful for users. It occurs to me that in LilyPond — Snippets <https://lilypond.org/doc/v2.25/Documentation/snippets/>, code precedes output. But those code snippets tend to be shorter. Often, when I see snippets on the Wiki that are not included in the official documentation, they include very long blocks of code. Here are a few examples of Wiki pages that I think would benefit especially from Luca’s suggested order, given how long their code blocks are — particularly for viewers on mobile devices, but also those on a computer. - Specifying number of measures per line <https://wiki.lilypond.community/wiki/Specifying_number_of_measures_per_line> - Unmetered music: An alternative to \cadenzaOn <https://wiki.lilypond.community/wiki/Unmetered_music:_An_alternative_to_%5CcadenzaOn> - Indenting individual systems <https://wiki.lilypond.community/wiki/Indenting_individual_systems> - Headers for all pages in bookpart <https://wiki.lilypond.community/wiki/Headers_for_all_pages_in_bookpart> Just my €0.02! Gabriel ---------- Forwarded message --------- From: Luca Fascione Date: Mon, 3 Nov 2025 Subject: Re: New LilyPond wiki replaces LSR This looks lovely thanks Jean, and thanks Sebastiano for the many years of support of LSR in its previous incarnation. Jean, forgive the bikeshedding, but is there a chance you could swap the order of presentation of the rendered music vs the lilypond source on the pages, so you get: Text description <beautiful notes> <beautiful source> I think when eyeballing a page to double check if this is in fact what one needs, seeing the score as-rendered first might be more intuitive for most people Thanks again for your work so far L -- Luca Fascione
