Public DomainImportant: By entering your snippet, you are placing it in the public domain. This includes also snippets taken from the Lilypond manual (the manual authors grant you their permission to do so).

The title should be a short, informative phrase describing your snippet. A continuative form like “Positioning accidentals…” is preferred.

This specifies the directory of this snippet on the LilyPond website. This field should normally be left blank.

Tags
Long description

Here's the place where to explain what the problem is, and how the snippet solves it. A direct form, such as “If you need to… you can…” is preferred.

You may use basic HTML formatting such as <code></code>, <em></em> or <q></q>. The syntax of your fragment will be checked, and all attributes will be stripped. Note that you can use any Unicode character, including, for instance, characters like ♪♫ or ❶❷➲—have a look at some character listing application for examples.

Lilypond snippet

Here comes the actual snippet. Try to make it small, so to let the main point emerge clearly. Please do not add a \version line—the snippet must compile on the currently running LilyPond version (see the contributions page).

Usually, before being compiled for visualisation snippets are prefixed by some Lilypond code that prints them in the right way for LSR. However, this prefix may disturb your snippet. If this happens, you might try to check the “standalone” checkbox, which will avoid the prefix, but that could cause problems.

If your snippet generates one or more full pages, you should check the “large” checkbox, which will compile the snippet at a lower resolution, collate the pages and thumbnail the result for better visualisation. In any case, the syntax of your code is checked with Lilypond, and, after submission, you can use the “Preview” button to have a look at the result. Note that large snippets will not be visualised in thumbnailed form during the preview, so don't get scared if they appear to be too big.