Simplify publish.sh strategy using direct git init approach

[konard]

🎯 Solution Overview

This PR implements a simpler publishing strategy for GitHub Pages deployment as requested in issue #8.

📋 Issue Reference

Fixes #8 - Attempt to use simpler strategy to publish files

🔧 Implementation Details

Previous Complex Approach (39 lines):

• Clone entire repository to access gh-pages branch
• Navigate between multiple directories
• Remove origin, add new origin
• Fetch and checkout gh-pages branch
• Delete all existing files
• Copy built files and commit

New Simplified Approach (32 lines):

• Build project locally with npm run export
• Navigate directly to out/ directory
• Initialize fresh git repository with git init
• Add all files and commit
• Add remote and force push to gh-pages branch

✨ Key Improvements

1. Reduced Complexity: Eliminates the need to clone the entire repository
2. Fewer Dependencies: No need to manage existing gh-pages branch state
3. Cleaner Logic: Direct git operations in the output directory
4. Performance: Faster execution without repository cloning
5. Maintainability: Easier to understand and debug

🔍 Technical Changes

The new script follows the Stack Overflow recommended approach for converting a directory into a git working directory:

1. git init - Initialize repository in output directory
2. git add --all - Stage all built files
3. git commit - Create deployment commit
4. git remote add origin - Connect to GitHub repository
5. git push -f origin gh-pages - Force push to gh-pages branch

🚀 Benefits

• Simpler maintenance: Less moving parts to break
• Better error handling: Clearer failure points
• Reduced resource usage: No need to clone large repositories
• Standard approach: Uses well-established git patterns

---

🤖 Generated with Claude Code