Playback of source material inside the transcript page
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Start with the transcript page and its media metadata field in the Hugo site. Define how YouTube videos and audio files are embedded, then trace how timestamped speaker segments can target playback positions; the work is done when both source types play in-page and timestamp clicks reach the corresponding segment.
Written by the indexing model from the issue text.
Description
Currently, each transcript on our platform includes a link to the original source material through the media metadata field. This allows readers to easily access the original content if they wish to.
The next step in enhancing user experience is to integrate the original source material directly into our transcript pages. Initially, we aim to support YouTube videos and audio files. For YouTube videos, embedding them within the page will provide seamless access. For audio files, implementing playback controls will enable users to listen to the content without leaving the transcript page.
Furthermore, for transcripts with timestamps for each speaker segment, we should introduce functionality where readers can click on a timestamp while reading and navigate to that specific segment in the playback source. This feature will allow users to listen to corresponding segments of the original content as they read through the transcript.
Inspiration for this functionality can be drawn from projects like the Optech podcast, where timestamps are provided for different segments, enhancing the reader's experience.
Further inspiration:
- Otter.ai playback
- https://scription.app/ (this is also something that we have previously discussed for enhancing the working-environment/editor in the Review product)
- Dominant language
- SCSS
- Stars
- 6
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bitcointranscripts/bitcointranscripts.github.io
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
high priority
bitcointranscripts/bitcointranscripts.github.io#62 · 2 assignees ·
-
high priority
bitcointranscripts/bitcointranscripts.github.io#61 · 2 assignees ·
-
high priority
Difficulty 3/5 1-2 days Newbie friendliness 40/100
bitcointranscripts/bitcointranscripts.github.io#60 · 1 comment ·
-
medium priority
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in bitcointranscripts/bitcointranscripts.github.io
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
task
Difficulty 2/5 1-3 hours Newbie friendliness 86/100