chore: move documentation .md files to docs directory

Moved BACKEND_QUICKSTART.md, BUILD_INSTRUCTIONS.md,
ELECTRON_QUICKSTART.md, and ELECTRON_README.md to docs/
directory to keep root clean (only dev.md remains in root)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: KevenWMarkham

BACKEND_QUICKSTART.md docs/BACKEND_QUICKSTART.mdBACKEND_QUICKSTART.md renamed to docs/BACKEND_QUICKSTART.md

@@ -24,11 +24,13 @@
 ### 2. Start PostgreSQL
 
 **Using Docker (easiest):**
+
 ```bash
 docker run --name transcript-postgres -e POSTGRES_DB=transcript_parser -e POSTGRES_USER=postgres -e POSTGRES_PASSWORD=postgres -p 5432:5432 -d postgres:15-alpine
 ```
 
 **OR use existing PostgreSQL and create database:**
+
 ```bash
 createdb transcript_parser
 ```
@@ -41,6 +43,7 @@ copy .env.example .env
 ```
 
 **Edit `.env` file** - Add your Gemini API key:
+
 ```env
 DATABASE_URL=postgresql://postgres:postgres@localhost:5432/transcript_parser
 JWT_SECRET=change-this-to-random-string-minimum-32-chars
@@ -63,6 +66,7 @@ npm run dev
 ```
 
 You should see:
+
 ```
 🚀 Server running on port 3000
 💾 Database: Connected
@@ -83,6 +87,7 @@ copy .env.example .env
 ```
 
 File should contain:
+
 ```env
 VITE_API_URL=http://localhost:3000/api
 ```
@@ -103,18 +108,22 @@ npm run dev
 ## Troubleshooting
 
 **Database won't connect?**
+
 - Check PostgreSQL is running: `docker ps` or check service
 - Verify DATABASE_URL in `.env`
 
 **FFmpeg error?**
+
 - Run `ffmpeg -version` to verify installation
 - Ensure FFmpeg is in your PATH
 
 **Gemini API error?**
+
 - Verify API key in `.env` is correct
 - Check quota at https://makersuite.google.com
 
 **Port 3000 in use?**
+
 - Change `PORT=3001` in server `.env`
 - Update frontend `.env`: `VITE_API_URL=http://localhost:3001/api`
 

BUILD_INSTRUCTIONS.md docs/BUILD_INSTRUCTIONS.mdBUILD_INSTRUCTIONS.md renamed to docs/BUILD_INSTRUCTIONS.md

@@ -15,6 +15,7 @@ ENOENT: no such file or directory, rename 'electron.exe' -> 'Transcript Parser.e
 The easiest solution is to build on a native x64 Windows machine:
 
 1. **On an x64 Windows computer**, clone the repo:
+
    ```bash
    git clone https://github.com/KevenWMarkham/transcript-parser
    cd transcript-parser
@@ -75,6 +76,7 @@ This works perfectly on ARM64 Windows and lets you test all desktop features.
 **For you right now**: Use GitHub Actions (Option 2)
 
 Benefits:
+
 - ✅ Builds on x64 servers (no ARM issues)
 - ✅ Completely automated
 - ✅ Builds for Windows, macOS, AND Linux
@@ -87,13 +89,15 @@ I can set this up in about 5 minutes if you'd like!
 ## 📝 Technical Details
 
 **Why this happens:**
+
 - You're on Windows ARM64
 - electron-builder uses `app-builder.exe` (ARM64 version on your machine)
 - app-builder ARM64 has bugs extracting x64 Electron binaries
 - The extraction fails silently, leaving `electron.exe` missing
 - Build fails when trying to rename non-existent file
 
 **Your options:**
+
 1. Build on x64 machine
 2. Use GitHub Actions (x64 cloud servers)
 3. Use WSL2 + Wine

ELECTRON_QUICKSTART.md docs/ELECTRON_QUICKSTART.mdELECTRON_QUICKSTART.md renamed to docs/ELECTRON_QUICKSTART.md

@@ -7,6 +7,7 @@ All Electron code is written and configured. You just need to build the `.exe` f
 ## 🔨 Build the Windows .EXE
 
 Run this command:
+
 ```bash
 npm run electron:build:win
 ```
@@ -18,6 +19,7 @@ The build might fail with `zip: not a valid zip file`. This is a temporary netwo
 **Solutions:**
 
 1. **Clear cache and retry:**
+
    ```bash
    npx electron-builder install-app-deps
    npm run electron:build:win
@@ -43,6 +45,7 @@ This launches the app in development mode with hot reload.
 ## 📦 After Build Succeeds
 
 You'll find in the `release/` folder:
+
 - `Transcript Parser-Setup-1.0.0.exe` - Full installer
 - `Transcript Parser-Portable-1.0.0.exe` - Portable version
 
@@ -51,6 +54,7 @@ Double-click to install and use!
 ## 🚀 Share Your App
 
 Once built, share the `.exe` file:
+
 - Upload to GitHub Releases
 - Share via Google Drive
 - Email directly

ELECTRON_README.md docs/ELECTRON_README.mdELECTRON_README.md renamed to docs/ELECTRON_README.md

@@ -5,50 +5,63 @@ Desktop version of the Transcript Parser built with Electron.
 ## Development
 
 ### Run in Development Mode
+
 ```bash
 npm run electron:dev
 ```
 
 This will:
+
 1. Start the Vite dev server
 2. Wait for it to be ready
 3. Launch Electron pointing to the dev server
 
 ### Build Standalone Executables
 
 #### Windows
+
 ```bash
 npm run electron:build:win
 ```
+
 Generates:
+
 - `release/Transcript Parser-Setup-1.0.0.exe` - Installer
 - `release/Transcript Parser-Portable-1.0.0.exe` - Portable version
 
 #### macOS
+
 ```bash
 npm run electron:build:mac
 ```
+
 Generates:
+
 - `release/Transcript Parser-1.0.0.dmg` - DMG installer
 - `release/Transcript Parser-1.0.0-mac.zip` - ZIP archive
 
 #### Linux
+
 ```bash
 npm run electron:build:linux
 ```
+
 Generates:
+
 - `release/Transcript Parser-1.0.0.AppImage` - AppImage
 - `release/Transcript Parser-1.0.0.deb` - Debian package
 - `release/Transcript Parser-1.0.0.rpm` - RPM package
 
 #### All Platforms
+
 ```bash
 npm run electron:build
 ```
 
 ## Features
 
 ### Native Desktop Features
+
 - ✅ Native file picker for video selection
 - ✅ Drag and drop video files
 - ✅ System tray integration
@@ -59,6 +72,7 @@ npm run electron:build
 - ✅ Auto-updates (when published to GitHub Releases)
 
 ### Keyboard Shortcuts
+
 - `Ctrl/Cmd + O` - Open video file
 - `Ctrl/Cmd + Q` - Quit application
 - `Ctrl/Cmd + R` - Reload
@@ -68,12 +82,14 @@ npm run electron:build
 ## Distribution
 
 ### GitHub Releases (Recommended)
+
 1. Build all platforms: `npm run electron:build`
 2. Create a new GitHub Release
 3. Upload the executables from the `release/` folder
 4. Users can download and install
 
 ### File Sizes
+
 - Windows Installer: ~150MB
 - macOS DMG: ~150MB
 - Linux AppImage: ~150MB
@@ -88,14 +104,17 @@ npm run electron:build
 ## Troubleshooting
 
 ### Windows
+
 - If SmartScreen blocks the app, click "More info" → "Run anyway"
 - For production, you should code-sign the executable
 
 ### macOS
+
 - If "app is damaged" message appears, run: `xattr -cr "/Applications/Transcript Parser.app"`
 - For production, you need an Apple Developer certificate
 
 ### Linux
+
 - Make AppImage executable: `chmod +x Transcript-Parser-1.0.0.AppImage`
 - Run: `./Transcript-Parser-1.0.0.AppImage`