Skip to content

Project Requirements

Executive Summary

The project aims to enhance the Multilingual Readers Program for ABC Head Start Society by developing a user-friendly web interface to allow teachers the ability to manage the contents of their pens. The current challenge faced by the Society is the complex audio file system of the pen, which is difficult for teachers to navigate and manage. Our project delivers an intuitive web interface for both teachers and administrators. Teachers can easily browse and download audio files for specific books, change languages for respective books, and manage the contents of their pens. Administrators gain a comprehensive management system for uploading new books, languages and managing the entire library.

Project Glossary

  • Add - A book or language and its associated details are inserted into the database.
  • Administrator - A user who can edit languages and books present on the interface by adding/deleting/replacing the contents. Along with this, Administrators have the same capabilities as Teachers do.
  • Audio Files - A file that contains an audio recording of a book in a particular language that is played when a sticker is scanned on a book. A set of audio files correspond to a specific language for a book.
  • Book - A physical book that has a collection of stickers, at least one on each page, that when scanned can read out contents of the page in up to four different languages.
  • Colours - Four colours on the front of each book which allows pen users to select one of four languages. The pen will then play the selected language for each page in the book.
  • Cybera - (Cybera)'s Rapid Access Cloud is infrastructure-as-a-service used to host and serve the web application to users
  • Download - Audio files are downloaded from Cybera onto the pen's local storage.
  • Language - A human language (such as English) used in the audio files. Users can access the specific languages available in the interface for transfer to digital pens.
  • Pen (Chameleon Reader) - A Chameleon Reader pen is a physical device that enables users to create and store their own audio recordings. The user scans a sticker, records their reading and then scans the sticker again to associate the sticker to the given audio recording. The pen can have a collection of books recorded in up to four different languages. Users have the flexibility to edit audio files through their computers file system by connecting the pen to the computer via micro USB.
  • Teacher - A user who has access to browse the books and languages on the pen and edit the contents of the pen with existing books and languages. The teacher can also download the audio files for a book and language to the pen.
  • Sticker - A small sticker on pages of books that the pen reads to play the audio file associated with that page. Each sticker has a unique number for identification.
  • Volume - A unit of storage on Cybera's Rapid Access Cloud infrastructure
  • Upload - Audio files are uploaded to the website and are then transferred to a volume for storage.

User Stories

Legend

US Number Feature
0.XX App environment set up
1.XX Teacher tasks
2.XX Administrator tasks
3.XX Audio File editing
4.XX Authentication

US 0.01.1 - Django Models

Story Points: 5

US 0.01.2 - MySQL database setup

Story Points: 5

US 0.01.3 - Docker Setup

Story Points: 5

US 0.01.4 - Cybera Deployment

Story Points: 5

US 0.01.5 - How to Page

Story Points: 2

As a teacher I want to be able to see a tutorial of how to navigate the website features so that I am able to know how to upload, browse, and download books and languages.

Acceptance Tests

  1. User can click a button that takes them to the "How To" page.
  2. How to page has steps on how to use all the Website's screens to download, browse, and upload books and languages.

US 1.01 - Browse Books

Story Points: 5

As a teacher I want to be able to browse books so that I can see all of the available books and their available languages.

Acceptance Tests

  1. User can scroll through a library of books with their title and book covers displayed.
  2. User can select a book and see the books details and languages available and for that book.
  3. User can navigate back to the library of books.

US 1.01.1 - Create Library/Book UI

Story Points: 2

As a teacher I want to be able to browse books so that I can see all of the available books and their available languages.

Acceptance Tests

  1. User can scroll through a library of books with their title and book covers displayed.
  2. User can select a book and see the books details and languages available and for that book.
  3. User can navigate back to the library of books.

US 1.01.2 - Create Endpoint to Retrieve Books

Story Points: 5

As a teacher I want to to be able to find books and book information so that I can see all of the available books and their available languages.

Acceptance Tests

  1. Frontend can send a GET request either for a specific book or all the books to the backend
  2. Backend will process the request
  3. Backend responds with the proper information to the frontend so that the user may know they were successful

US 1.02 - Filter by Language

Story Points: 3

As a teacher I want to be able to filter books by language so that I can see all of the available books in a specific language.

Acceptance Tests

  1. User can select a language or languages from a checkbox list in the filter section.
  2. The library of books is updated when a filter is applied.
  3. User can clear the filter and see all books again.
  4. If the user selects multiple languages, the library is updated to show books that are available in any of the selected languages.

US 1.02.1 - Language Filter UI

Story Points: 1

As a teacher I want to be able to click a checkbox to filter books by language so that I can see all of the available books in a specific language.

Acceptance Tests

  1. User can select any number of languages from a checkbox list
  2. User can click a clear button to reset the filter and see all books again
  3. The library is updated to show books that are available in any of the selected languages

US 1.02.2 - Create end-point to retrieve books by filtered language

Story Points: 2

As a user I want a way to retrieve books associated with a language so that I may find relevant information quicker

Acceptance Tests

  1. Frontend can send a GET request to the backend for language information
  2. Backend validates request and returns books associated with the language
  3. Backend gives an appropriate response to the frontend so that the user may know they were successful

US 1.03 - Download Audio Files

Story Points: 8

As a teacher I want to be able to download the audio files for my selected book and language to my pen so that the pen can be used with the physical book.

Acceptance Tests

  1. User can preview/play the audio files for their selected book and language.
  2. User can see what languages are already downloaded on the pen for their selected book, with their designated colours.
  3. User can select which language they want to replace if the selected book already has four languages downloaded on the pen.
  4. User can select an empty colour if the selected book has less than four languages downloaded on the pen.
  5. User confirms the download of recording for their selected book and language.
  6. User can see the progress of the download indicating the download status and estimated time remaining.
  7. User is notified when the download is successful.
  8. The files will be automatically downloaded to the correct locations in the pen filesystem.
  9. User receives an error notification if the download fails, specifying the reason for the failure.

US 1.03.1 - Download Audio Files UI

Story Points: 1

As a teacher I want to be able to click a button to download the audio files for my selected book and language to my pen so that the pen can be used with the physical book.

Acceptance Tests

  1. User can see what languages are already downloaded on the pen for their selected book, with their designated colours.
  2. User can select which language they want to replace if the selected book already has four languages downloaded on the pen.
  3. User can select an empty colour if the selected book has less than four languages downloaded on the pen.
  4. User confirms the download of recording for their selected book and language.
  5. User can see the progress of the download indicating the download status and estimated time remaining.
  6. User is notified when the download is successful.

US 1.03.2 - Index File on Pen

Story Points: 3

As a teacher I want to be able to see the contents of my pen and see the changes to the books and languages on my pen where applicable, this can be done through the index file on the pen.

Acceptance Tests

  1. Backend Pen interface can access the user's file system
  2. Backend Pen interface can write to the index.json file on the pen, creating it if necessary
  3. Backend Pen interface can update the index file with a new book, language, folder
  4. Backend Pen interface can request the DB for specific audio files corresponding to a book and language.

US 1.03.3 - Retrieve Files from Cybera Volumes

Story Points: 8

As a teacher I want to be able to download the audio files for my selected book and language to my pen so that the pen can be used with the physical book.

Acceptance Tests

  1. System retrieves the audio files from the Cybera volume for the selected book and language

US 1.03.4 - Download Audio Files

Story Points: 5

As a teacher I want to be able to download the audio files for my selected book and language to my pen so that the pen can be used with the physical book.

Acceptance Tests

  1. Audio files for the selected book and language are downloaded to the pen
  2. The pen is updated with the new audio files
  3. The pen is usable with the physical book

Story Points: 3

As a teacher I want to be able to search for a book by title so that I can find a specific book without needing to scroll through the list of books.

Acceptance Tests

  1. User can type a search term into a search bar.
  2. User is shown a list of books that match the search term.
  3. List of books is updated as the user types.
  4. Auto-complete/suggestions are shown as the user types.
  5. If no books match the search term, the user is notified.
  6. User can clear the search and see all books again.
  7. Search is case-insensitive and matches partial words.
  8. Search is efficient even with a large number of books.

US 1.04.1 - Search Bar UI

Story Points: 1

As a teacher I want to be able to search for a book by title so that I can find a specific book without needing to scroll through the list of books.

Acceptance Tests

  1. User can type a search term into a search bar.
  2. User is shown a list of books that match the search term.
  3. List of books is updated as the user types.
  4. Auto-complete/suggestions are shown as the user types.
  5. If no books match the search term, the user is notified.
  6. User can clear the search and see all books again.
  7. Search is case-insensitive and matches partial words.

US 1.05 - Pen Details

Story Points: 5

As a teacher I want to be able to check the contents of my pen so that I can see the books and recordings that are stored on the pen.

Acceptance Tests

  1. User can navigate to a page to manage the books and languages on the pen through a dedicated button on the home page.
  2. User is prompted to connect a pen to the device if no pen is connected.
  3. User receives a notification when they connect the pen to the device.
  4. User can scroll through a library of books with their title and book covers displayed.
  5. User can select a book and see the books details and the recordings for that book with their associated colour.

US 1.05.1 - Pen Details UI

Story Points: 2

As a teacher I want a page to see information about my pen so that I know what books and languages are on the pen

Acceptance Tests:

  1. The books displayed on the UI are the same as the books listed on the index file
  2. The languages the books are available in are the same as the ones listed on the index file

US 2.01 - Add Book

Story Points: 3

As an administrator I want to be able to add a new book to the library so that I can update the library when a new physical book is obtained.

Acceptance Tests

  1. User can press a button to begin the process of adding a new book.
  2. User can enter the title of the book.
  3. User can choose the book cover image.
  4. User can press a button to submit the new book entry.
  5. User is notified when the addition is successful.
  6. The book object is added to the database.
  7. The book and its uploaded language are available for selection in the library.
  8. User can edit the book details after the book is added.
  9. Empty fields are denied and the user is notified the field is required.
  10. Duplicate books are denied and the user is notified the book already exists.

US 2.01.1 - Add Book to SQL Database

Story Points: 3

As a administrator I want to be able to add books to the database so that I can add a new physical book to the library.

Acceptance Tests

  1. Frontend can send a POST request to the backend with book information
  2. Backend will validate information and store new book
  3. Backend will give an appropriate response to the Frontend so that the user may know they were successful

US 2.01.2 - Add Book UI

Story Points: 3

As an administrator I want to be able to add a new book to the library so that I can update the library when a new physical book is obtained.

Acceptance Tests

  1. User can press a button to begin the process of adding a new book.
  2. User can enter the title of the book.
  3. User can choose the book cover image.
  4. User can press a button to submit the new book entry.
  5. User is notified when the addition is successful.
  6. The book and its uploaded language are available for selection in the library.
  7. User can press a button to edit the book details after the book is added.
  8. Empty fields are denied and the user is notified the field is required.
  9. Duplicate books are denied and the user is notified the book already exists.

US 2.02 - Add Language

Story Points: 2

As an administrator I want to be able to add a new language to a book so that teachers can have access to a new language for a book.

Acceptance Tests

  1. User can press a button to begin the process of adding a new language.
  2. User can enter the language name.
  3. User presses a button to submit the new language entry.
  4. User is notified when the addition is successful.
  5. The language is added to the database.
  6. The language is available for selection.
  7. Empty fields are denied and the user is notified the field is required.
  8. Duplicate langugaes are denied and the user is notified the language already exists.

US 2.02.1 - Add Language to SQL Database

Story Points: 3

As a administrator I want to be able to add languages to the database so that I can later on add recordings that are in that language to the database.

Acceptance Tests

  1. Frontend can send a POST request to the backend with language information
  2. Backend will validate information and store new language
  3. Backend will give an appropriate response to the Frontend so that the user may know they were successful

US 2.02.2 - Add Language UI

Story Points: 1

As an administrator I want to be able to add a new language to a book so that teachers can have access to a new language for a book.

Acceptance Tests

  1. User can press a button to begin the process of adding a new language.
  2. User can enter the language name.
  3. User presses a button to submit the new language entry.
  4. User is notified when the addition is successful.
  5. The language is displayed in the list of available languages for the book.
  6. User can press a button to edit the language details after the language is added.
  7. Empty fields are denied and the user is notified the field is required.
  8. Duplicate langugaes are denied and the user is notified the language already exists.

US 2.03 - Delete Book

Story Points: 3

As an administrator I want to be able to delete a book so that I can update the catalog of books if a physical book is no longer available.

Acceptance Tests

  1. User can select a book and can press a button to delete the book.
  2. User is prompted to confirm the deletion, with an option to cancel.
  3. The book object is deleted from the database.
  4. User is notified when the deletion is successful.
  5. The book is longer available for selection.

US 2.03.1 - Delete Book from SQL Database

Story Points: 2

As an administrator I want to be able to delete books from the database so that I can manage my database accordingly Acceptance Tests

  1. Frontend can send a DELETE request to the backend and remove a book from the database
  2. Backend validates request and deletes the book from the database
  3. Backend gives an appropriate response to the frontend so that the user may know they were successful

US 2.03.2 - Delete Book UI

Story Points: 1

As an administrator I want to be able to delete a book so that I can update the catalog of books

Acceptance Tests

  1. User can select a book and can press a button to delete the book.
  2. User is prompted to confirm the deletion, with an option to cancel.
  3. User is notified when the deletion is successful.
  4. The book is no longer available for selection.

Story Points: 1

As an administrator I want a way to delete a book from the database as a whole so that I can manage my database accordingly

Acceptance Tests

  1. Frontend can send a DELETE request to the backend and remove a book from the database
  2. Backend validates request and deletes the book from the database
  3. Backend validates request and deletes the book from a specific book
  4. Backend gives an appropriate response to the Frontend so that the user may know they were successful

US 2.04 - Delete Language

Story Points: 2

As an administrator I want to be able to delete a language from a book so that I can update the available languages for a book if a language is no longer needed.

Acceptance Tests

  1. User can navigate to a page to manage the all available languages.
  2. User can select a language and can press a button to delete the language.
  3. User is prompted to confirm the removal, with an option to cancel.
  4. The language and all of the book-language associations are deleted from the database.
  5. The user is notified when the deletion is successful.
  6. The language is no longer available for selection.
  7. User can also choose to delete a singluar language from a specific book.

US 2.04.1 - Delete Language from SQL Database

Story Points: 1

As an administrator I want a way to delete languages both associated with a book and from the database as a whole so that I can manage my database accordingly

Acceptance Tests

  1. Frontend can send a DELETE request to the backend and remove a language from the database
  2. Frontend can send a DELETE request to the backend and remove a language from a specific book
  3. Backend validates request and deletes the language from the database
  4. Backend validates request and deletes the language from a specific book
  5. Backend gives an appropriate response to the Frontend so that the user may know they were successful

US 2.04.2 - Delete Language UI

Story Points: 1

As an administrator I want to be able to delete a language from a book so that I can update the available languages for a book if a language is no longer needed. Acceptance Tests

  1. User can navigate to a page to manage the all available languages.
  2. User can select a language and can press a button to delete the language.
  3. User is prompted to confirm the removal, with an option to cancel.
  4. The user is notified when the deletion is successful.
  5. The language is no longer available for selection.
  6. User can also choose to delete a singluar language from a specific book.

US 2.05 - Sticker Replacement

Story Points: 5

As an administrator, I want to be able to add new sticker numbers to existing pages, so that when a sticker is accidentally removed from a book I can fix it by adding a new one.

Acceptance Tests

  1. User can find and select a book by browsing.
  2. User can see existing pages and what sticker numbers are associated with them.
  3. User can add new sticker-to-page associations to a selected book through a menu.
  4. User can update the book in the database when prompted.
  5. User can enter number of new sticker.
  6. User can download the book and the audio files will be added to the pen in the locations for both the new sticker number and the existing ones.

US 2.05.1 - Sticker Replacement UI

Story Points: 1

As an administrator, I want to interact with a user interface to add new sticker numbers to existing pages, so that when a sticker is accidentally removed from a book I can fix it by adding a new one.

Acceptance Tests

  1. User can find and select a book by browsing.
  2. User can see existing pages and what sticker numbers are associated with them.
  3. User can add new sticker-to-page associations to a selected book through a menu.
  4. User presses a button to submit the new sticker association.
  5. User is notified when the addition is successful or unsuccessful.

US 2.05.2 - Endpoint for Sticker Association

Story Points: 3

As an administrator, I want to be able to be able to create new sticker associations for a book so that I can fix any issues with the stickers in the book.

Acceptance Tests

  1. Frontend can send a POST request to the backend with sticker association information
  2. Backend will give an appropriate response to the Frontend so that the user may know they were successful
  3. Backend will update the book in the database with the new sticker association

US 2.05.3 - Add a New Sticker to the Database

Story Points: 2

As an administrator, I want to be able to add a new sticker to the database so that I can store the new sticker association for a book.

Acceptance Tests

  1. Frontend can send a POST request to the backend with sticker information
  2. Backend will validate information and store new sticker
  3. Sticker association ia added to the database and can be retrieved by the backend

US 2.05.4 - Manage Sticker/File in Pen API

Story Points: 3

As an administrator, I want to be able to manage the stickers and files in the pen so that my pen can be updated to reflect the changes made to the book/sticker associations.

Acceptance Tests

  1. Backend Pen interface can the database for the new sticker association
  2. Backend Pen interface can update the index file with the new sticker association
  3. Backend Pen interface can request the DB for specific sticker association corresponding to a book and language.
  4. Backend Pen interface can associate the new sticker association with the existing audio files

US 2.06 - Upload Audio Files

Story Points: 5

As an administrator, I want to be able to upload audio files to the website so that I can download these files to a pen later

Acceptance Tests

  1. User can click a button on a book details page to begin the process of uploading audio files.
  2. User can select a language that corresponds to the audio files they are uploading.
  3. User can select and upload files from local device.
  4. User can see the progress of the upload indicating the upload status and estimated time remaining.
  5. User is notified when the upload is successful.
  6. The files will be automatically uploaded to the correct locations in the cybera volume.
  7. User receives an error notification if the upload fails, specifying the reason for the failure.

US 2.06.1 - Pointer to Database

Story Points: 2

As an administrator, I want to be able to store the location of the audio files in the database so that I can download these files to a pen later

Acceptance Tests

  1. Frontend can send a POST request to the backend with audio file information
  2. Backend will validate information and store new audio file location
  3. Backend will give an appropriate response to the Frontend so that the user may know they were successful
  4. Backend can retrieve the location of the audio files from the database

US 2.06.2 - Upload Audio Files UI

Story Points: 1

As an administrator, I want to interact with a user interface to upload audio files to the website so that I upload my audio files to the database.

Acceptance Tests

  1. User can click a button on a book details page to begin the process of uploading audio files
  2. User can select a language that corresponds to the audio files they are uploading
  3. User can select and upload files from local device
  4. User can see the progress of the upload indicating the upload status and estimated time remaining
  5. User is notified when the upload is successful
  6. User is notified when the upload fails, specifying the reason for the failure

US 2.06.3 - Upload Audio Files

Story Points: 2

As an administrator, I want to be able to upload audio files to the website so that I can download these files to a pen later

Acceptance Tests

  1. Audio files are uploaded to the website
  2. The files are stored in the correct locations in the cybera volume
  3. The files are available for download to the pen
  4. The files are associated with the correct book, language, sticker number and colour

US 3.01 - File Conversion

Story Points: 8

As an administrator I want to be able to covert file types so that I can upload any audio file format and have it converted to the correct format for the pen.

Acceptance Tests

  1. When uploading audio files for a book or language, the user can upload any audio file format.
  2. The user is notified the format is not supported.
  3. The user is prompted to convert the file.
  4. The user can press a button to begin the conversion.
  5. The user can see the progress of the conversion.
  6. The user is notified when the conversion is successful.
  7. The user can see the converted file.

US 3.01.1 - FFmpeg File Conversion Backend

As a user I want the app to be able to convert the format of audio files so that I can ensure the file format is compatible with the pen

Acceptance Tests

  1. Backend has FFMPEG integrated to convert format of audio files
  2. Backend has an endpoint to accept files and returns converted files

US 3.02 - File Trim

Story Points: 8

As an administrator I want to be able to trim audio files so that I can remove any unwanted parts of the audio file.

Acceptance Tests

  1. After uploading an audio file, the user can press a button to begin the trimming process.
  2. The user can select what portion of the audio file they want to trim.
  3. The user can see the progress of the trimming.
  4. The user is notified when the trimming is successful.
  5. The user can see the trimmed file.

US 3.02.1 - FFmpeg File Trim

Story Points: 5

As a administrator I want the app to be able to trim audio files so that I can remove any unwanted parts of the audio file

Acceptance Tests

  1. Backend has FFMPEG integrated to trim audio files
  2. Backend has an endpoint to accept files and returns trimmed files

US 3.02.2 - File Trim UI

Story Points: 3

As an administrator I want to be to interact with a user interface to trim audio files so that I can remove any unwanted parts of the audio file

Acceptance Tests

  1. User can select a page to trim the file
  2. User can select a file to trim
  3. User can select the portion of the file to trim
  4. User can press a button to begin the trimming
  5. User can see the progress of the trimming
  6. User is notified when the trimming is successful
  7. The user can download the trimmed file
  8. User receives an error notification if the trimming fails, specifying the reason for the failure

US 3.03 - File Merge

Story Points: 8

As an administrator I want to be able to merge audio files so that I can combine multiple audio files into one file.

Acceptance Tests

  1. After uploading an audio file, the user can press a button to begin the merging process.
  2. The user can select what audio files they want to merge.
  3. The user can see the progress of the merging.
  4. The user is notified when the merging is successful.
  5. The user can see the merged file.

US 3.03.1 - FFmpeg File Merge

Story Points: 5

As a user I want the app to be able to merge audio files so that I can combine multiple audio files into one file

Acceptance Tests

  1. Backend has FFMPEG integrated to merge audio files
  2. Backend has an endpoint to accept files and returns merged files
  3. Backend can merge multiple audio files into one file
  4. Backend can merge audio files of different formats
  5. Backend can merge audio files of different lengths

US 3.03.2 - File Merge UI

Story Points: 3

As an administrator I want to be to interact with a user interface to merge audio files so that I can combine multiple audio files into one file

Acceptance Tests

  1. User can select a page to merge the file
  2. User can select multiple files to merge
  3. User can press a button to begin the merging
  4. User can see the progress of the merging
  5. User is notified when the merging is successful
  6. The user can download the merged file
  7. User receives an error notification if the merging fails, specifying the reason for the failure

US 4.01 - Authentication

Story Points: 8

As a user I want to be able to login to the application as either a teacher or administrator so that I can use the application.

Acceptance Tests

  1. Teachers are prompted to log in using Microsoft OAuth2 when first accessing the website.
  2. Administrators are prompted to log in using Microsoft OAuth2 when first accessing the website.
  3. Teachers can only browse books, view book details and download audio files.
  4. Administrators can perform all actions including browsing, downloading, adding, and deleting books and languages.
  5. Unauthorized users/invalid credentials cannot successfully log in and receive an error message.

US 4.01.1 - Authentication System

Story Points: 5

As a user I want to be able to login to the application as either a teacher or administrator so that I can use the application in a secure manner.

Acceptance Tests

  1. Backend has an authentication system in place
  2. Backend can authenticate users with specified username and passowrds

US 4.01.2 - Hiding Based on Permissions

Story Points: 3

As a user I want to be able to see different parts of the application based on my permissions so that I can use the application according to my role.

Acceptance Tests

  1. Teachers can only browse books, view book details and download audio files.
  2. Administrators can perform all actions including browsing, downloading, adding, and deleting books and languages.
  3. Unauthorized users/invalid credentials cannot successfully log in and receive an error message.
  4. Unauthorized users cannot access the admin panel.

MoSCoW

Must Have

  • US 1.01 - Browse Books
  • US 1.03 - Download Audio Files
  • US 2.01 - Add Book
  • US 2.02 - Add Language
  • US 2.05 - Sticker Replacement
  • US 2.06 - Upload Audio Files
  • US 4.01 - Authentication

Should Have

  • US 1.02 - Filter by Language
  • US 1.04 - Search Bar
  • US 1.05 - Pen Details

Could Have

  • US 2.03 - Delete Book
  • US 2.04 - Delete Language

Would Like But Won't Get

  • US 3.01 - File Conversion
  • US 3.02 - File Trim
  • US 3.03 - File Merge

Similar Products

File System Access API Local MarkDown Editor

  • Local file editor for Markdown files
  • Demonstrates the (relatively) new File System API, which allows browsers to perform CRUD operations on the client file system.
  • Inspiration for how we will interface with the user's pen with a web application.

Google Play Books

  • Digital book store
  • Allows users to browse and download books in a user-friendly interface
  • Inspiration for a user-interface for browsing books, including a search bar and filtering.

Open-Source Projects

shadcn/ui

  • UI Library
  • Provides numerous pre-made UI components
  • Inspiration for UI, UX, and general aesthetics; open source allows us to make use of these components to ramp up front-end development.

FFmpeg

  • Multimedia (video and audio) Processing
  • Allows audio trimming and processing
  • Inspiration for how to complete audio manipulation user stories

Librivox

  • Free Public Domain Audiobooks
  • Demonstrates a large collection of audio files for books in different languages.
  • Inspiration for a user interface for browsing and downloading audio files.

Technical Resources

Backend: Django, MySQL, NextAuth

Deployment: Docker + Cybera

Frontend: Next.JS (React + TypeScript), File System API