Main AppLayout is updated with a new UI that includes permalink frontend and sizing fix-ups #37. These changes need to be added to PermLayout.

We need to save file uploads to GCP to be able to render it in permalink frontend later

Also, add videoResource key in the of the transcriptionResult document that points to the streamable video link

• Improve Dockerfile
• Create image
• Push image to Repository
• Deploy to Cloud Run
• Redirect Firebase Hosting
• Make the app live!

• use classes instead of hooks
• move critical functions send...ToBackend to AppLayout
• declutter ImportVideo
• Render input on video player

• Input bar (file dropdown/URL)
• submit
• headers
• requests to backend
• spinner
• snackbars 🍫
  - [ ] backend validation microservice for links

The path is broken and the logo does not render in the README. Try changing the slashes in path from \ to /

Also, a better alt text like transcribio logo would be great

@knightcube hoping you can take this up

• set up a speech to text service (Google/Azure ?)
• send audio files to get transcriptions
• process transcriptions (through native algorithm/NLP offerings)
• deploy to backend

• Render the download transcript button
• Create the backend API endpoint for getting full transcript
• Implement file downloading

The UI component be deployed to a hosting service (preferably Firebase)

Will help testing lay the foundation for backend deployment in the near future

Permalinks will open in a separate view fetching data that has been processed before and stored on the database.

This view will have to be designed and implemented.

Additional task :

• Snackbars post processing

• Video player
• Keyword display
• Link keyword to seek time
• Download transcript

• Search bar/form
• Create backend API endpoint for getting timestamps for a certain keyword input
• Display keyword & timestamps output

• UI for displaying keyword & timestamps
• Integrate the timestamp & seeking mechanism from #9

Currently, our app only supports url of videos that are uploaded to the cloud. We want to extend this first to Youtube urls, and later on to any video sources.

• Render the video player
• Timestamp and seeking mechanism

The permalink feature will require data to be stored and retrieved on the frontend.

We have to finalize a database structure for the feature.

• generate permalink post-processing
• structure database
• save data to database
• show data on a permalink request

generate a unique hash-id to be used as a permalink for the video content.

Add captioning to video player using the generated transcript - or display the full transcript and highlight the sentence that the video is currently on

• sending the video (file/URL)
• getting permalink
• internal APIs (if backend is designed as microservices)

• perform locally as a PoC
• deploy on the backend

Render the main keywords from #25