Scripture reference issues

Yes, I was thinking a bit about it. There are two possible variants. Technically both need a a second database field.
One variant is like it's done for the speaker: two individual fields and you (or the layout) decide which one you want to show where. This needs also second field in the editing form.
The other variant is like it's done for the Joomla articles. There you can set a "readmore" line, which then splits the content internally and shows either only the intro or full text (but not only the second part).

I tend to the first variant, so it's similar to the speaker. Imho it also allows a bit more flexibility.

I agree, I think your first idea is allows more control and suits the purpose better.

You can try the attached version.
You will have to enable the new field in the SermonSpeaker options in the "columns" section for the views you want ti to show.. Otherwise it will not display in frontend.

Nice one!
I did a test on this sermon, httn.net/audio-teachings/sermon/83-the-b...essianic-communities and its working very well. I'll probably modify the template to put the main text into a scrollable div so that the page focus visibility can remain at the top while reading but this is probably user side preference stuff.
I suspect this will also make very significant different for SEO visibility too. Thank you so much!

Yet another small user-friendly suggestion, with the "Audio file size" move away from using bytes to human friendly Mb, everything thinks in terms of 93M not 93300000.

A side idea, I wonder if you could develop a paid feature with a player that support time-coded transcription to the text follows that audio. I'm not sure if there's a market for it but just a thought.

I've added a class ss-maintext to the surrounding element. That will help customize it.

as for the bytes: The ? field behind will show you the value in a human readable format
Ideally, you don't have to fill it in the value manually anyway. If SermonSpeaker can access the file, it can read the size itself when you click on the magic wand behind the filename (the one that reads the ID3 tags).