These instructions will get you a copy of the web frontend up and running on your local machine for development and testing purposes.
- Node.js: Required to run the web frontend locally.
- Install Node.js: Download and install the latest version from https://nodejs.org/en/download/.
- Install dependencies:
npm install
- Run the project:
npm start
Update your local repository: Before submitting, make sure your local branch is up to date with the remote main branch to avoid conflicts:
git pull origin main
Local testing: Run and test your changes locally to ensure everything works as expected and no errors are introduced.
Selective file staging: Only add files related to your changes. Avoid staging all files at once.
Recommended approach:
git add src/routes/Settings/index.tsx
git add src/components/TextToSpeech/TTS.tsx
This helps prevent unrelated files (such as logs or environment files) from being committed.
Use short and clear commit messages that describe the purpose of your changes:
git commit -m "feat(settings): add voice controls"
Choose your branch prefix based on the type of work:
For new features: git push origin feature/your-branch-name
For bug fixes: git push origin fix/your-branch-name
This makes it easier for the team to understand the purpose of the branch.
- Log in to GitHub and navigate to the project repository.
- Click Pull requests → New pull request.
- On the new PR page:
- Set the base branch to main
- Set the compare branch to your pushed branch.
- Click Create pull request.
Title: Provide a brief summary of the changes, e.g.:
- feat(settings): add voice controls
- fix(navbar): resolve overlap issue
Description (must include the following):
- List of modified or new files
- A short explanation of the main changes
- Related screenshots or recordings
Example:
## Modified or New Files
- src/routes/Settings/index.tsx (new)
- src/components/TextToSpeech/TTS.tsx (modified)
## Change Summary
- Added voice control sliders
- Improved TTS component responsiveness
## Screenshots

After creating the PR, make sure to invite two project leads as Reviewers. Reviewers will either:
- Approve and merge the code, or
- Leave comments with feedback for changes.
If reviewers request changes:
- Make the required changes locally
- Run git add and git commit again
- Push to the same branch:
git push origin feature/your-branch-name
GitHub will automatically update the existing PR with your new commits.
Once the reviewers approve and merge into the main branch, the PR is considered complete. No further manual task updates are required—the team will confirm the status after merging.