Documentation

Welcome to the mei-friend Documentation pages! Please use the navigation menu to switch between topics. To dive straight in, you can also have a look at our quickstart guide and consult our handy cheat sheet listing all available keyboard shortcuts and URL parameters.

The documentation is split into Basic topics and Advanced topics.

We recommend to begin your exploration with Getting started.

Caveats

Development of both the mei-friend editor, and the documentation available on this site, are on-going community efforts. The information presented here is thus subject to constant change. We will endevour to keep all claims presented here as factual and as current as possible. However, please do not be surprised if, for example, screenshots look slightly outdated by the time you view them; the mei-friend interface may have changed since the most recent time of writing. Please help us keep this documentation correct, complete, and up-to-date by raising issues on our issue tracker as required.

The mei-friend editor is developed under an AGPL v3 license. While we endevour to positively contribute to your music encoding enjoyment and success, and aim to ensure the stability, safety, and security of all data and workflows operated upon by mei-friend, please be aware of the terms outlined within this license, particularly sections 16 (disclaimer of warranty) and 17 (limitation of liability).

See the ‘About’ page for more information about contributors, funding, and licensing.

Conventions

We adhere to the following conventions within the documentation chapters presented here:

Fonts

We use monospace fonts when refering directly to labeled elements of the mei-friend interface, particularly when instructing you to interact with them, e.g., Click on Help->Show documentation to access the mei-friend documentation website.

We also use monospace fonts when refering to specific MEI elements or attributes. When talking about elements, we will use one of two styles: either, e.g., as: the measure element or more directly as: <measure>. When discussing specific attributes, we will refer to, e.g.,: <measure@n> when talking about an attribute in the context of an element, or just: @n when talking generally about an attribute. Wherever possible, that is, whenever we are talking about an element or an attribute in the context of an element, we will link to the relevant page of the MEI Guidelines (pointing at the list of attributes when appropriate).

Call-outs

We use three kinds of call-out to convey tidbits of information at first glance, aiming to catch your eye as you are browsing through the documentation: