Hey folks, I’ve continued to push updates to my Astro LilyPond integration.
https://lilypond.ky.fyi It now supports: • Writing and outputting scores inside Markdown • Generating automatic `alt` text for images based on the “title” and “composer” in the header of a score • Support for outputting multi-page scores inside semantic ordered list elements • Integration with Astro’s content collections (point your site at a folder full of .ly files and it will allow you to query and display them on individual pages or on an index) • Ability to automatically install and cache the LilyPond binary for rendering scores when building and deploying the site via CI (GitHub Actions, Cloudflare, Netlify, Vercel, etc.) The end result of this integration is you can treat .ly files like any other code in a codebase and use them to compile nice SVG or PNG images to display to users who view your site. I’ve copied over the official LilyPond examples <https://lilypond.ky.fyi/examples/> to demonstrate the integration working in practice. Give it a spin and comment or file an issue if you run into any bugs. It’s still pre-v1.0, but I’m hoping not to make too many more breaking API changes before then. https://lilypond.ky.fyi Ky PS Still interested in if anyone knows of a systematic way to increase spacing between staves when “crop” is on. On Sun, Jul 19, 2026, at 11:26 AM, Ky Decker wrote: > Hi! > > I'm building an integration for Astro which allows compiling and displaying > LilyPond scores: > > https://lilypond.ky.fyi > > Currently I'm setting `crop` on all scores by default in order to help with > responsive web design and prevent unnecessary whitespace on webpages. > > However, the `crop` default causes spacing between staff groups to be overly > tight, see examples: > > https://lilypond.ky.fyi/examples/ > > Is there any way to reserve a reasonable amount of space between staves when > enabling `crop`? > > Ky Decker
