Add client-side text-to-speech option for articles #245
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a client-side “Listen to article” option using the browser’s native Web Speech API.
The feature is fully client-side, opt-in, and does not require any backend or build-time changes.
Scope is intentionally limited to UI and client-side JavaScript changes related to Issue #197.
Note: While attempting to test locally with
mkdocs serveon Windows, I encountered MkDocs plugin configuration errors unrelated to this feature. I have intentionally not included any configuration or dependency changes in this PR to avoid scope creep, but I can open a follow-up PR if maintainers would like those issues addressed.Fixes #197