diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml
new file mode 100644
index 0000000..8ef7bda
--- /dev/null
+++ b/.github/workflows/deploy.yml
@@ -0,0 +1,31 @@
+name: Build and Deploy to GitHub Pages
+
+on:
+ push:
+ branches:
+ - main # Change to your default branch if different
+
+jobs:
+ build:
+ runs-on: ubuntu-latest
+
+ steps:
+ - name: Checkout Repository
+ uses: actions/checkout@v3
+
+ - name: Setup Node.js
+ uses: actions/setup-node@v3
+ with:
+ node-version: '23'
+
+ - name: Install Dependencies
+ run: npm install
+
+ - name: Build Project
+ run: npm run build
+
+ - name: Deploy to GitHub Pages
+ uses: peaceiris/actions-gh-pages@v3
+ with:
+ github_token: ${{ secrets.GITHUB_TOKEN }}
+ publish_dir: ./build # Directory to publish
\ No newline at end of file
diff --git a/README.md b/README.md
index 382941e..411bd31 100644
--- a/README.md
+++ b/README.md
@@ -1,47 +1,49 @@
-# Svelte + Vite
+# Face Blit Web
-This template should help get you started developing with Svelte in Vite.
+This project brings [Face Blit](https://github.com/AnetaTexler/FaceBlit) to a web application for demonstration purposes.
-## Recommended IDE Setup
+## Usage
-[VS Code](https://code.visualstudio.com/) + [Svelte](https://marketplace.visualstudio.com/items?itemName=svelte.svelte-vscode).
+1. **Clone the repository:**
-## Need an official Svelte framework?
+ ```bash
+ git clone https://github.com/Yushu-He/FaceBlit-Web.git
+ cd FaceBlit-Web
+ ```
-Check out [SvelteKit](https://github.com/sveltejs/kit#readme), which is also powered by Vite. Deploy anywhere with its serverless-first approach and adapt to various platforms, with out of the box support for TypeScript, SCSS, and Less, and easily-added support for mdsvex, GraphQL, PostCSS, Tailwind CSS, and more.
+2. **Install dependencies:**
-## Technical considerations
+ ```bash
+ npm install
+ ```
-**Why use this over SvelteKit?**
+3. **Run the development server:**
-- It brings its own routing solution which might not be preferable for some users.
-- It is first and foremost a framework that just happens to use Vite under the hood, not a Vite app.
+ ```bash
+ npm run dev
+ ```
-This template contains as little as possible to get started with Vite + Svelte, while taking into account the developer experience with regards to HMR and intellisense. It demonstrates capabilities on par with the other `create-vite` templates and is a good starting point for beginners dipping their toes into a Vite + Svelte project.
+## Technologies Used
-Should you later need the extended capabilities and extensibility provided by SvelteKit, the template has been structured similarly to SvelteKit so that it is easy to migrate.
+- [Svelte](https://svelte.dev/)
+- [WebAssembly (Wasm)](https://webassembly.org/)
+- [MediaPipe](https://github.com/google/mediapipe)
+- [IDB](https://github.com/jakearchibald/idb)
+- [Font Awesome](https://fontawesome.com/)
+- [Vite](https://vitejs.dev/)
-**Why `global.d.ts` instead of `compilerOptions.types` inside `jsconfig.json` or `tsconfig.json`?**
+## Note
-Setting `compilerOptions.types` shuts out all other types not explicitly listed in the configuration. Using triple-slash references keeps the default TypeScript setting of accepting type information from the entire workspace, while also adding `svelte` and `vite/client` type information.
+In the main branch, there is a TypeScript native version, but due to time constraints, it is only partially completed and has low performance.
-**Why include `.vscode/extensions.json`?**
+## Conclusion
-Other templates indirectly recommend extensions via the README, but this file allows VS Code to prompt the user to install the recommended extension upon opening the project.
+This project was developed as the final project for the University of Michigan EECS442 course.
-**Why enable `checkJs` in the JS template?**
+## References
-It is likely that most cases of changing variable types in runtime are likely to be accidental, rather than deliberate. This provides advanced typechecking out of the box. Should you like to take advantage of the dynamically-typed nature of JavaScript, it is trivial to change the configuration.
-
-**Why is HMR not preserving my local component state?**
-
-HMR state preservation comes with a number of gotchas! It has been disabled by default in both `svelte-hmr` and `@sveltejs/vite-plugin-svelte` due to its often surprising behavior. You can read the details [here](https://github.com/sveltejs/svelte-hmr/tree/master/packages/svelte-hmr#preservation-of-local-state).
-
-If you have state that's important to retain within a component, consider creating an external store which would not be replaced by HMR.
-
-```js
-// store.js
-// An extremely simple external store
-import { writable } from 'svelte/store'
-export default writable(0)
-```
+- [Face Blit](https://github.com/AnetaTexler/FaceBlit)
+- [MediaPipe](https://github.com/google/mediapipe)
+- [Mediapipe 2 Dlib Landmarks by PeizhiYan](https://github.com/PeizhiYan/Mediapipe_2_Dlib_Landmarks/tree/main)
+- [Build TFLite & OpenCV to WASM (with SIMD, CMake) | Face Detection on Web](https://blog.seeso.io/face-detection-on-web-tflite-wasm-simd-462975e0f628)
+- University of Michigan EECS442 Course Materials
\ No newline at end of file
diff --git a/index.html b/index.html
index 5e41629..34201cf 100644
--- a/index.html
+++ b/index.html
@@ -3,6 +3,7 @@