ada-blazor-wasm-github-pages

Publish with dotnet publish, then ensure the artifact root is publish/wwwroot containing a .nojekyll file and a 404.html copied from index.html. Use actions/upload-pages-artifact and actions/deploy-pages in a GitHub Actions workflow with pages: write and id-token: write permissions.

GitHub Pages runs Jekyll by default, which discards directories starting with underscores like _framework. Add an empty .nojekyll file to the artifact root. Also verify the artifact path is publish/wwwroot, not the publish directory itself.

Copy index.html to 404.html in the publish output so GitHub Pages serves it for unmatched paths, letting Blazor route after startup. For project-level sites, also set the base href to /<repo>/ in index.html.

The wwwroot/data directory is gitignored because it is generated at build time by the content converter tool. Run the converter manually before dotnet run, otherwise every data/*.json request fails at runtime rather than at build time.

No, python http.server lacks SPA fallback so sub-routes return 404 instead of index.html. Use the included spa-server.js script, which falls back to index.html for extensionless paths and mimics GitHub Pages 404.html behavior.

Using Element.Value on nested structures like <field><text lang="zh">A</text><text lang="en">B</text></field> concatenates child text into AB. Parse with parent.Elements(name) plus the lang attribute as a dictionary, using direct lang attributes on fields.