Here you can see how you could do something like that. Each audiofile in the collection gets it's own section, where you can add information and images, and then you can page through the sections and click on the mp3 files, to listen to them.
Sorry that the Asciidoc formatting doesn't let you see the pictures, yet. It actually looks quite pretty, with the original book covers from Beatrix Potter. I think nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn still has markdown formatting setup, but I made him a ngit issue for it.
Here's how each section looks, in my code editor preview. You could also format the sections with a table, so that it looks like on the original webpage. https://librivox.org/the-tale-of-peter-rabbit-and-others-by-beatrix-potter/ Then it's horizontal formatting, rather than vertical.
👀 🔥
I think this makes it more clear, why we wanted Asciidoc, instead of markdown. People can use these event types for high-quality publishing, with stylesheets and complex tables, side bars, etc.
Can't even adjust image size, with markdown.
I just did this real quick, so I didn't color the background or center the text in the columns, or anything, but this gives you an idea of what the table-based orientation looks like in the viewer.
Each section is a separate event, they're just linked together in a row by the index event. You can change which sections are included, or edit the content of the sections, after the fact, as they are parameterized replaceable.
Someone who is writing a wiki page about Beatrix Potter, could (theoretically, they haven't implemented it, yet) take the first section only, and place that event in the wiki page, as a quote or reference.
Yes!
