Summary
User-facing docs are landing in-repo as an Astro Starlight site (website/, see #11). This issue tracks publishing that site — domain, Cloudflare Pages (or equivalent), CI deploy, and who owns DNS/access.
Needs co-ordination with @ni5arga (repo owner / ops).
Why separate from #11
#11 is content and docs-as-code. Hosting needs maintainer decisions: which account hosts Pages, custom domain (if any), whether downloads/checksums live on the same origin, and who can trigger deploys.
Proposed setup (open to change)
- Build:
website/ Astro Starlight on push to main (rootDirectory website)
- Host: Cloudflare Pages (static; easy to mirror)
- CI: GitHub Action or Cloudflare’s Git integration
- Trust: signed APK/IPA (or TestFlight) + checksums when distribution starts; keep “only trust a build you compiled or one from a source you trust” on the site
Decisions needed from maintainer
Done when
Summary
User-facing docs are landing in-repo as an Astro Starlight site (
website/, see #11). This issue tracks publishing that site — domain, Cloudflare Pages (or equivalent), CI deploy, and who owns DNS/access.Needs co-ordination with @ni5arga (repo owner / ops).
Why separate from #11
#11 is content and docs-as-code. Hosting needs maintainer decisions: which account hosts Pages, custom domain (if any), whether downloads/checksums live on the same origin, and who can trigger deploys.
Proposed setup (open to change)
website/Astro Starlight on push tomain(rootDirectorywebsite)Decisions needed from maintainer
*.pages.devfor nowmainonly, or also PR previewsDone when
website/README.mdor CONTRIBUTING