Reader component location

[MegumiKim]

Currently Reader component lives inside the LMS package, but it should live inside the TTS package and be imported by LMS.

[Anclagen]

I think the component should be further abstracted to allow for separation of concerns.

• I would say more of the logic functions should be pulled out of the reader into the TTS. Functions such as fetchAudio, createAudio, and related state management (e.g., hasAudio, audioSrc, etc.).
• Separate the page details fetching logic. You could have a separate utility function that manages fetching page details this could probably be used else where in the LMS too.
• UI part of the reader should remain in the LMS
• Another thing to consider would be to create a notification manager too, to standardize usage across other components too.

In a previous issue #60 we also discussed the TTS being installed on its own server to manage creation, storage, and serving of the files so the reader component itself would simply be requesting a specific lessons file from here.

[Fermain]

I have that magic server, so we can do free TTS with slightly below Elevenlabs quality.

Molly exports one component and an HTTP method - I like that pattern as it makes it easy to intergrate into any Sveltekit project. I think LMS should have theme control over the reader, but I'm ok with it being abstracted away as well.

[Fermain]

To complete, migrate the Reader component to TTS repo as an importable component