song2html-claude-plugin

song2html

Song charts are translated into HTML so they can be displayed and stylized in a web browser.

Example Input Format

Songs need to be specifically formatted as follows:

Title
  author: John Doe, Jane Doe
  key: C
  tempo: 128
  time: 4/4
  
  verses: A B C  D E F
  chorus: D E F  A B C
  bridge: G A B  C D E

Sections:
  Verse 1:
    ^Some lyrics ^are here
    ^carets are ^where chords ^go
    ^oh
  
  Chorus:
    ^If the ^section name starts with the ^same word as the section in the ^chord chart ^(after the title)
    it will use those chords in the ^section

  Verse 2:
    ^For example, all ^verses will all
    ^use the same chords, and chord-naming is ^pretty flexible.
    ^You can even use ^Nashville numbering.
  
  Bridge:
    ^Don't forget the colons, ^they're important.
    And if you have more carets than chords, it will just start at the beginning of the chord chart and keep going.

Arrangements:
  Live:
    Verse 1
    Chorus
    Verse 2
    Chorus
    Bridge
  
  Studio:
    Verse 1
    Verse 2
    Chorus
    Verse 1
    Chorus
    Bridge
    Chorus

Format Specification

• There will always be a default arrangement which displays the sections in the order they are given.
• Parsing rules:
  • Blank lines are ignored
  • Windows line-endings (\r\n) and Unix line-endings (\n) are both supported.
• The very first line of the file is the song title.
  • Everything indented beneath the title is metadata about the song.
  • The following are some internally recognised song vars:
    • key
    • tempo
    • time
    • author
    • Other keys are presumed to be section names for chord charts.
      • Any chords after the section-name <song-section-name>: are assumed to be chords for that section- even if they span multiple lines.
      • Groups of chords in parentheses can be repeated by a following xN, where N is the number of times to repeat.
        • e.g. (C G Am F)x2 would expand to C G Am F C G Am F
• Segments
  • Segments are defined by a name followed by a colon.
  • Segments indented under the segment name belong to that segment.
    • 2-space indentation is used to define segments & metadata.
    • 4-space indentation is used to define content within song-sections and arrangements.
  • Segment names are not case-sensitive; i.e. 'Arrangements' is the same as 'arrangements'.
  • Segments names cannot be:
    • key
    • tempo
    • time
    • author
  • The following are reserved segment names:
    • Arrangements
    • Sections
  • Segements beneath 'Sections' are song sections.
    • These segments can be named anything.
    • If a section name starts with the same word as a section in the chord chart (after the title), it will use those chords in that section.
      • e.g. 'Chorus' in the chord chart will be used in any section named 'Chorus', 'Chorus 1', 'Chorus A', etc.
    • Carets within the song sections indicate where chords go.
      • Chords are mapped from the corresponding chord chart metadata.
      • If there are more carets than chords in a line of lyrics, it will loop back to the beginning of the chord chart and continue assigning chords.
  • Segments beneath 'Arrangements' are arrangements.
    • These segments can be named anything.
    • Each line in an arrangement is the name of a song-section to include in that arrangement in the given order.
    • If no arrangements are defined, the default arrangement is used (which is the sections in the order written.)
• Output is paginated
  • First "page" is the title block, metdata, and chord chart
  • Subsequent pages contain song sections
  • Pages are separated after a certain number of lines (configurable in code)

Example Output