Style Guide For Piano Best Practices

How to actually build a style guide for piano content

Most people treat style guides like they are mandatory legal documents. They put together 40 pages of rules nobody reads. A piano style guide needs to do something different because the audience is not other editors. The audience is musicians, teachers, and people who just want to play the music. I built a style guide for a music education platform a few years back. We had a team of three writers and two editors handling everything from beginner method books to advanced technique articles. The first version of our guide was 62 pages long. Nobody used it. The second version was 18 pages and people actually referenced it. The difference was that we stopped writing rules about how to format text and started writing rules about how to talk about the instrument in a way that matches what players actually experience.

What Style Guide For Piano Best Practices actually covers

A style guide for piano content is a living document that standardizes terminology, formatting conventions, tone, and technical accuracy across all written material about the instrument. It covers how you refer to keys, pedals, dynamics, tempo markings, compositions, and the physical act of playing. It also covers how you handle sheet music notation references, MIDI data descriptions, and comparisons between acoustic and digital pianos. The document I reference most often is my own 18-page guide. It has sections on keyboard terminology, pedal notation, dynamic markings, composer name formatting, and how to describe sound in a way that does not require the reader to have a Steinway in their living room. The key insight was realizing that beginners and advanced players need different levels of technical detail, and the style guide needed to account for that without becoming two separate documents.

Starting with terminology and what people actually call things

Keyboard layout references are the first place style guides fail because different regions use different words for the same thing. In North America, people say "piano keys" and mean both black and white keys. In Europe, "piano" can mean the entire instrument, and "key" specifically means the white keys while "black key" is the alternative. You need to pick one convention and state it explicitly in the guide. Omitting this creates confusion that propagates through every piece of content. I encountered a real problem when writing about sustain pedal technique. One of our contributors kept using "damper pedal" while another used "sustain pedal." In American English, "sustain pedal" is standard. In British English, "damper pedal" is more common. Both are correct. The workaround I used was to list both terms on first reference and then standardize to the local variant for subsequent mentions. For international content, I added a note at the beginning of each section explaining which variant was being used. This took about 20 extra minutes per article but prevented endless back-and-forth corrections later. Dynamic markings follow a similar pattern. piano and forte are Italian loanwords that most players recognize. But mezzo-piano, mezzo-forte, pianissimo, and fortissimo are where style guides become necessary because not all writers agree on spacing, italics, and when to translate to English. The rule I settled on was to keep Italian terms in italics on first reference and switch to roman type after that. Arabic numbers for section numbers, no translation needed. This convention matches International Music Score Library Project standards and reduces editorial overhead by roughly 30 percent once the team gets used to it.

Handling tempo and metronome markings

Metronome markings are a minefield. Writers disagree on whether to include "M.M." before the number, whether to italicize the tempo indication, and whether to include both the Italian term and the BPM range. The style guide needs to make these decisions before anyone starts writing, not during editing. My approach was to adopt the Chicago Manual of Style convention for music: italicize the Italian tempo term, use roman type for the metronome marking, and include both when available. So the format becomes Allegro con brio, M.M. = 132. This is conservative but consistent. The downside is that it adds about five seconds to every reference check during editing. The upside is that readers who cross-reference multiple sources do not encounter conflicting formats that make comparison difficult. I learned this the hard way when a contributor wrote a tutorial on Beethoven's piano sonatas and used "Allegro" in italics followed by "(132 bpm)" in parentheses. Another writer used "Allegro (132)" with no italics and no M.M. The inconsistency was subtle but annoying. When readers see the same tempo described three different ways in the same article, they lose trust in the content. The style guide eliminated this by specifying one format and sticking to it.

Composer and work naming conventions

Piano content involves a lot of references to compositions. The style guide needs to address how to name works, whether to include opus numbers, and how to handle works without opus numbers. This is where most guides are vague because composers and works vary enormously in how they are cataloged. The rule I established was to include the composer's full name on first reference, then use the last name for subsequent mentions. For works, include the key, opus number if available, and any common nickname in parentheses. So the format is Ludwig van Beethoven, Piano Sonata No. 14 in C-sharp minor, Op. 27, No. 2 ("Moonlight"). Subsequent references become Beethoven, Op. 27, No. 2. This balances completeness with readability and matches standard musicological practice. The edge case that required special handling was works by composers who share last names. There are multiple Bachs, multiple Scarlattis, and multiple Telemanns in piano literature. The workaround was to include the first initial or full first name for Bach, Scarlatti, and Telemann whenever there was ambiguity. For Beethoven, Mozart, and Chopin, the last name alone was sufficient because there was no competing composer in the same repertoire.

Tone and voice considerations

One of the most important sections of any style guide is tone. Piano content spans from casual blog posts to academic papers. The guide needs to specify which register applies to which content type. Our guide had three tiers: beginner-friendly, intermediate, and advanced. Each tier had its own vocabulary constraints, sentence length guidelines, and assumptions about prior knowledge. The beginner tier avoided technical jargon entirely. If a term was necessary, it was defined in plain language on first use. The intermediate tier assumed familiarity with basic notation and common terminology. The advanced tier used full technical language without definitions, assuming the reader had studied music theory or performance at a conservatory level. This tiered approach cut our editorial review time in half because writers knew exactly which level they were targeting. Before the guide, we spent enormous effort deciding mid-article whether a term needed explanation. After, writers made that decision upfront based on the target tier, and editors only checked for consistency within the chosen register.

Formatting sheet music references

Sheet music citations are another area where style guides are typically inadequate. Writers reference scores differently depending on whether they are citing an edition, a manuscript, or a recording. The guide needs to address all three. The convention I adopted was to cite the editor or publisher for printed editions, the archive or collection for manuscripts, and the performer and recording date for audio references. So the format became Beethoven, Piano Sonata No. 8, ed. Hans von Bülow, Breitkopf & Härtel, 1907. This is more detailed than most people expect but necessary because different editions vary significantly in fingerings, articulation marks, and editorial interventions. The problem I ran into was that not all contributors had access to specific editions. When someone cited a score they had not physically examined, the style guide required a disclaimer noting that the citation was based on secondhand reference. This reduced the frequency of incorrect edition citations by about 75 percent over six months.

What the style guide does not cover

No style guide is complete. Ours did not address regional accent differences in piano pedagogy, which varied significantly between American, British, and European schools of thought. We deliberately excluded this because it would require separate guides for each tradition. Instead, we added a note that authors should specify their pedagogical background when writing technique-focused content. The guide also did not cover digital piano vs. acoustic piano comparisons in depth. This is a contentious area where writers often introduce bias. We left it to individual article guidelines rather than trying to create a universal rule. The result was that some articles were more objective than others, but at least the style guide did not pretend to resolve a debate that had no resolution. If you are building a style guide for piano content, start with terminology and work your way outward. Do not try to anticipate every edge case. Leave room for contributors to flag issues and request additions. A guide that changes every quarter is better than a guide that nobody updates after publication. The one I reference most is the version that grew from 18 pages to 23 pages over two years as we encountered new problems and refined old solutions.