Test kwelea-generated sites on common static hosting platforms

[engineervix]

Context

kwelea build produces a fully static site — no server-side logic, no CDN dependencies, self-contained assets. It should deploy cleanly to any static host, but each platform has its own routing conventions, build pipeline requirements, and redirect handling that can surface edge cases.

GitHub Pages has been verified. This issue tracks compatibility testing across the remaining major platforms.

Checklist

Hosting platforms

• GitHub Pages -- via GitHub Actions -- https://engineervix.github.io/kwelea/
• Cloudflare Pages -- direct upload / wrangler or Git integration -- https://kwelea.pages.dev/
• Vercel -- static output via vercel --prod
• Netlify -- drag-and-drop or netlify deploy --prod
• Render -- static site service
• AWS S3 + CloudFront -- bucket static hosting
• Surge.sh -- surge site/
• Firebase Hosting -- firebase deploy

Things to verify on each platform

• All pages load (no 404 on nested routes like /guide/configuration/)
• Assets resolve correctly (CSS, JS, fonts under /assets/)
• Search works (FlexSearch loads search-index.json via relative path)
• Dark/light mode toggle persists across page navigations
• Prev/Next navigation links work
• base_url in kwelea.toml matches the deployed URL (needed for canonical links if/when added)
• No mixed-content warnings in browser console

Notes

• Platforms that rewrite index.html URLs (e.g. serve /guide/configuration without trailing slash) may need a _redirects or vercel.json rule — document any workarounds found.
• If a platform requires a build command, go install github.com/engineervix/kwelea@latest && kwelea build should be sufficient.
• Add a docs page under guide/deployment.md for any platform-specific steps discovered here.

How to contribute

Pick a platform from the list, deploy the kwelea docs site or your own project, and report your findings as a comment — what worked, what didn't, and any config you needed to add.