Enhance Vite configuration to dynamically set base path for GitHub Pages deployment

Author: gunta

.github/workflows/deploy.yml

@@ -0,0 +1,50 @@
+name: Deploy to GitHub Pages
+
+on:
+  push:
+    branches: [main]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: pages
+  cancel-in-progress: true
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: npm
+
+      - name: Install dependencies
+        run: npm install
+
+      - name: Build site
+        run: npm run build
+
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: dist
+
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

AGENTS.md

@@ -0,0 +1,16 @@
+# Repository Guidelines
+
+## Project Structure & Module Organization
+Synth is a Vite + React TypeScript project. Keep application logic inside `src/`, with `main.tsx` bootstrapping React and `App.tsx` arranging top-level layout. Reusable UI lives in `src/components/` using PascalCase filenames, while shared styles stay in `src/index.css` and design tokens in `tailwind.config.js`. Serve static assets from `public/`; avoid committing anything generated under `dist/`.
+
+## Build, Test, and Development Commands
+Install dependencies with `npm install` (or `bun install` to respect `bun.lockb`). Use `npm run dev` for a hot-reloading development server. Run `npm run build` to compile a production bundle and surface TypeScript errors. Validate the built output locally via `npm run preview`. Keep the codebase lint-clean with `npm run lint`.
+
+## Coding Style & Naming Conventions
+Use TypeScript throughout and prefer functional React components. Follow the existing two-space indentation and wrap JSX attributes to multiple lines when they exceed the formatter width. Name components and their files in PascalCase (`Logo.tsx`), hooks in camelCase (`useFeatureFlag`), and utility modules with kebab-case if added outside `components/`. Tailwind utility classes should describe layout-to-appearance order, matching current patterns. Linting is configured via `eslint.config.js`; fix or justify any warnings before opening a pull request.
+
+## Testing Guidelines
+No automated test harness ships yet, so rely on `npm run lint` and manual verification until tests are introduced. When adding tests, colocate them beside components using the `Component.test.tsx` pattern and prefer React Testing Library with Vitest for consistency with the Vite ecosystem. Document any new test commands in `package.json` and reference them here.
+
+## Commit & Pull Request Guidelines
+History favors concise, action-oriented commit messages (e.g., `Update layout spacing`). Write messages in the imperative mood and group related changes per commit. For pull requests, provide a summary of the user-facing effect, link any tracking issues, and attach screenshots or recordings when UI changes are involved. Note any follow-up tasks and ensure `npm run build` and `npm run lint` have been run before requesting review.

vite.config.ts

@@ -1,10 +1,15 @@
 import { defineConfig } from 'vite';
 import react from '@vitejs/plugin-react';
 
-// https://vitejs.dev/config/
-export default defineConfig({
-  plugins: [react()],
-  optimizeDeps: {
-    exclude: ['lucide-react'],
-  },
+// Configure Vite to serve assets from the repository path when deployed to GitHub Pages.
+export default defineConfig(() => {
+  const repoName = process.env.GITHUB_REPOSITORY?.split('/')?.[1];
+
+  return {
+    base: repoName ? `/${repoName}/` : '/',
+    plugins: [react()],
+    optimizeDeps: {
+      exclude: ['lucide-react'],
+    },
+  };
 });