[KnobeDev]

Summary

Adds built-in ChordPro lead-sheet rendering to the plugin — chord-and-lyric sheets from chopro / chordpro code blocks, alongside the existing engraved notation. Two commits:

1. Feature — a self-contained renderer (src/chordpro/chordProBlock.ts, no dependencies) registered as chopro/chordpro code-block processors in main.ts, plus lead-sheet styling in styles.css. It renders independently of the Verovio engraving engine (ChordPro carries no pitch/rhythm to engrave).
2. Docs — a (NEW) ChordPro Lead Sheets README section (syntax + accessibility), and a credit under Additionally Used (With Many Thanks).

What it renders

```chopro
{title: Sweet Home Alabama}
{key: D}

[D]Big wheels keep on [C]turnin'
[G]Carry me home to see my [D]kin
```

Supports inline [chords], directives ({title:}, {key:}, {comment:}, arbitrary key: value), and labelled {start_of_chorus} / verse / bridge / tab sections.

Accessibility

Screen-reader-first: DOM order is chord-then-syllable (a reader hears "G chord, Carry me home to see my, D chord, kin"), chords carry an aria-label so Am isn't read as the word "am", the title is a heading, choruses/verses are labelled groups, and chords are set apart by weight + position — never colour alone (WCAG 1.4.1).

Credit

The renderer is an independent reimplementation — seeing ChordPro Viewer by jheddings is what sparked the idea, and it's built in this plugin's own way (no code shared). Because both claim the chopro/chordpro code-block languages, the README notes you'd disable one or the other. Credited in the README as a shout-out.

Notes

• Contributed by jdhori.
• Type-checks cleanly against the base (adds 0 new tsc errors).
• Excludes version bumps and the built main.js bundle — those are the maintainer's call to rebuild/release.

[kpaede]

Hi, thanks for the contribution!

I'm not entirely sure whether ChordPro rendering fits the scope of this plugin. Since it works independently of Verovio, it wouldn't benefit from most of the existing functionality, such as score editing, MEI conversion, MIDI playback, or interactive notation. It would basically be a separate plugin wrapped together with this one. I'm wondering whether this functionality might be better suited to a dedicated ChordPro plugin, especially since those already exist for Obsidian.

Could you share your thoughts on why you think this should be integrated this plugin? From a user's perspective, I think it would be quite confusing to suddenly have a different code block logic, especially when most of the features that make this plugin useful wouldn't be available with that format.

Of course, one could consider expanding the plugin to support all kinds of other formats and rendering systems. But the whole idea behind its current state is that (since it's using Verovio) everything is internally converted to MEI and managed through that common representation. That's what allows the different formats to benefit from the same features and workflows.

Introducing a separate rendering system that bypasses this architecture would basically break that and make the plugin less consistent overall. So while I appreciate the contribution, I'm not convinced that this approach fits the plugin's architecture and intended scope.