Adds dedicated workflow for CVClaude branch deployment

Splits deployment logic into separate workflows for better maintainability
- Creates new workflow for CVClaude branch targeting /360 subfolder
- Updates main workflow to only deploy main branch
- Simplifies build configuration by removing branch detection logic
- Improves documentation to reflect the new architecture

Author: EtienneLescot

.github/workflows/cvclaude-360.yml

@@ -0,0 +1,66 @@
+# Workflow for deploying cvclaude branch to 360 subfolder
+name: Deploy CVClaude to 360 subfolder
+
+on:
+  # Runs on pushes targeting the cvclaude branch
+  push:
+    branches: ["cvclaude"]
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
+# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
+concurrency:
+  group: "pages-360"
+  cancel-in-progress: false
+
+jobs:
+  # Single deploy job since we're just deploying
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          ref: cvclaude
+      
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+      
+      - name: Install dependencies
+        run: npm install
+      
+      - name: Build project for 360 subfolder
+        run: npm run build
+        env:
+          BASE_PATH: /cv/360
+      
+      - name: Prepare 360 deployment directory
+        run: |
+          mkdir -p 360
+          mv *.html *.css *.js 360/ 2>/dev/null || true
+      
+      - name: Setup Pages
+        uses: actions/configure-pages@v5
+      
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          # Upload 360 directory
+          path: '360'
+      
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

.github/workflows/static.yml

@@ -2,9 +2,9 @@
 name: Deploy static content to Pages
 
 on:
-  # Runs on pushes targeting the main and cvclaude branches
+  # Runs on pushes targeting the main branch only
   push:
-    branches: ["main", "cvclaude"]
+    branches: ["main"]
 
   # Allows you to run this workflow manually from the Actions tab
   workflow_dispatch:
@@ -25,7 +25,7 @@ jobs:
   # Single deploy job since we're just deploying
   deploy:
     environment:
-      name: github-pages
+      name: ${{ github.ref == 'refs/heads/main' && 'github-pages' || 'github-pages-cvclaude' }}
       url: ${{ steps.deployment.outputs.page_url }}
     runs-on: ubuntu-latest
     steps:

MULTI_BRANCH_DEPLOYMENT.md

@@ -9,15 +9,18 @@ This project now supports deploying multiple branches to GitHub Pages with diffe
 
 ## Architecture
 
-### GitHub Actions Workflow
+### GitHub Actions Workflows
 
-The [`static.yml`](.github/workflows/static.yml) workflow has been modified to:
+Two separate workflows handle the deployments:
 
-1. **Trigger on both branches**: Runs on pushes to `main` and `cvclaude` branches
-2. **Branch Detection**: Uses conditional logic to determine deployment path
-3. **Dynamic Path Configuration**:
-   - `main` branch → root deployment (`.`)
-   - `cvclaude` branch → subfolder deployment (`360`)
+#### Main Branch Workflow ([`static.yml`](.github/workflows/static.yml))
+- **Trigger**: Runs on pushes to `main` branch only
+- **Deployment**: Deploys to root path (`.`)
+
+#### CVClaude Branch Workflow ([`cvclaude-360.yml`](.github/workflows/cvclaude-360.yml))
+- **Trigger**: Runs on pushes to `cvclaude` branch only
+- **Deployment**: Deploys to `/360` subfolder
+- **Configuration**: Uses `BASE_PATH=/cv/360` environment variable
 
 ### Build Process Modifications
 
@@ -50,22 +53,19 @@ GitHub Pages Structure:
 
 ## How It Works
 
-### 1. Branch Detection
+### 1. Separate Workflows
 
-The workflow detects the current branch using `github.ref`:
+Each branch has its own dedicated workflow:
 
-```yaml
-- name: Determine deployment path
-  id: deployment-path
-  run: |
-    if [[ "${{ github.ref }}" == "refs/heads/cvclaude" ]]; then
-      echo "DEPLOYMENT_PATH=360" >> $GITHUB_OUTPUT
-      echo "BASE_PATH=/cv/360" >> $GITHUB_OUTPUT
-    else
-      echo "DEPLOYMENT_PATH=." >> $GITHUB_OUTPUT
-      echo "BASE_PATH=/cv" >> $GITHUB_OUTPUT
-    fi
-```
+**Main Branch Workflow** ([`static.yml`](.github/workflows/static.yml)):
+- Triggers on `main` branch pushes
+- Builds with default settings (root deployment)
+- Deploys files to root directory
+
+**CVClaude Branch Workflow** ([`cvclaude-360.yml`](.github/workflows/cvclaude-360.yml)):
+- Triggers on `cvclaude` branch pushes
+- Builds with `BASE_PATH=/cv/360` environment variable
+- Moves files to `360/` subdirectory before deployment
 
 ### 2. Build Configuration
 
@@ -98,15 +98,13 @@ if (CONFIG.basePath) {
 
 ### 4. Deployment
 
-Files are moved to the appropriate directory before upload:
+For CVClaude branch, files are moved to the 360 subdirectory:
 
 ```yaml
-- name: Prepare deployment directory
+- name: Prepare 360 deployment directory
   run: |
-    if [[ "${{ steps.deployment-path.outputs.DEPLOYMENT_PATH }}" != "." ]]; then
-      mkdir -p ${{ steps.deployment-path.outputs.DEPLOYMENT_PATH }}
-      mv *.html *.css *.js ${{ steps.deployment-path.outputs.DEPLOYMENT_PATH }}/ 2>/dev/null || true
-    fi
+    mkdir -p 360
+    mv *.html *.css *.js 360/ 2>/dev/null || true
 ```
 
 ## Testing