Deploy Device Toolbox website with GitHub Pages

[Copilot]

This PR implements GitHub Pages deployment for the Device Toolbox website, a Vite-based application using TypeScript and Lit web components.

Changes Made

Vite Configuration

• Updated vite.config.ts to set the correct base path (/toolbox/) for GitHub Pages deployment in production
• Ensures all assets (JS, CSS, images) are served with the proper path prefix

GitHub Actions Workflow

• Added .github/workflows/deploy.yml for automated build and deployment
• Configures Node.js environment, runs linting, builds the project, and deploys to GitHub Pages
• Includes proper permissions for GitHub Pages deployment

Single Page Application (SPA) Support

• Added public/404.html to handle client-side routing on GitHub Pages
• When users navigate directly to routes like /toolbox/vpe, GitHub Pages serves the 404.html which redirects to the main app
• Updated index.html with redirect handling script to restore correct URLs from the 404 redirect

Router Updates

• Modified src/utils/router.ts to properly handle the base path
• Strips the /toolbox prefix in production while maintaining clean internal routing
• Ensures navigation between pages works correctly with the base path

Testing Results

The deployment has been thoroughly tested locally:

• ✅ Homepage loads correctly with proper styling at /toolbox/
• ✅ Client-side routing works for detail pages (/toolbox/vpe, /toolbox/zwa2)
• ✅ Navigation between pages functions seamlessly
• ✅ Direct URL access works through 404.html redirect mechanism
• ✅ No security vulnerabilities detected
• ✅ All existing lint rules pass

Screenshots

Homepage:

Detail Page (ZWA-2):

Deployment

Once merged, the website will be automatically deployed to GitHub Pages at https://openhomefoundation.github.io/toolbox/. The repository settings need to be configured to enable GitHub Pages with "GitHub Actions" as the deployment source.

The build process includes:

1. Installing dependencies
2. Running ESLint for code quality
3. Building the optimized production bundle
4. Deploying to GitHub Pages

All changes maintain backward compatibility and don't affect the development workflow.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/OpenHomeFoundation/OpenHomeFoundation%2Ftoolbox/languages
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Deploy this website with github pages

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[balloob]

@copilot I've added a domain to the main branch in CNAME. It is https://toolbox.openhomefoundation.org

[balloob]

@copilot we don't want this. Remove it.