docs: remove unnecessary content from README.md

This commit is contained in:
Mueez Khan 2024-01-09 00:42:34 -05:00 committed by GitHub
parent 8210e463e1
commit 525a57b1f9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -9,13 +9,12 @@ A website showcasing the ability to overlay custom subtitles for multiple YouTub
1. Create captions for a YouTube video and save them as a `.vtt` file.
1. One method is using online caption-making software or Adobe Premiere Pro, exporting as a `.srt` file and then converting it to a `.vtt` file using an online conversion tool.
2. Rename the `.vtt` file to the video ID of the YouTube video.
1. For example if the YouTube video you're captioning is at [https://www.youtube.com/watch?v=-JTq1BFBwmo](https://www.youtube.com/watch?v=-JTq1BFBwmo) then the video ID is after the `=` symbol as `-JTq1BFBwmo`.
1. For example if the YouTube video you're captioning is at https://www.youtube.com/watch?v=-JTq1BFBwmo then the video ID is after the `=` symbol as `-JTq1BFBwmo`.
3. Add the `.vtt` file to `/src/captions/` and add the video ID to the array in `captions.js`.
4. Build the React application and deploy it.
1. You can use tools like [Vercel](https://vercel.com/) or [Netlify](https://www.netlify.com/) to automate this process.
## Conclusions
This was helpful in understanding how to work with the [Video.js](https://videojs.com/) player and adding my own custom subtitles.
This was helpful in understanding how to work with the Video.js player and adding my own custom subtitles.
There is a possible issue where adding more caption entries may result in a single row of selectable videos to become too crowded/long, so this could be fixed. Though I don't plan to as this isn't a production application and there are web applications such as [Amara.org](https://amara.org/) and [Captionfy](https://www.captionfy.com/) that are more fully featured.
There is a possible issue where adding more caption entries may result in a single row of selectable videos to become too crowded/long, so this could be fixed. Though I don't plan to as this isn't a production application.