claude@clouddev1
a72d53de51
Record the deployment decision (2026-06-11): static build deploys to Cloudflare (Workers static assets or Pages; no Astro adapter needed), driven by a planned Gitea Actions pipeline. Update the ADR-website-001 index entry to match.
Website Architecture Decision Records
Decision records for the public website + documentation site subproject
(the Astro/Starlight site under website/). These are kept in their own
namespace, separate from the project-wide ADRs in
docs/adr/, so website decisions never compete with
the main global ADR sequence for numbers — see
ADR-0000 "Numbering discipline".
Numbering. Files are named <date>-adr-website-<NNN>.md and referenced
in prose as ADR-website-NNN. The <date> (the ADR's accepted/created day,
YYYYMMDD) plus the website segment keeps the namespace disjoint from
main's integers. Assign the next free NNN from this index. Every ADR
change updates this index in the same edit (the ADR-0000 index-upkeep rule
applies here too).
Index
- ADR-website-001 — Public website and documentation site — Accepted 2026-06-04 (formerly ADR-0044 in the main index; moved here 2026-06-10 to end recurring cross-branch number collisions). The first public website: a marketing landing page plus the canonical user docs. Stack Astro 6 + Starlight + Tailwind v4 (chosen over SvelteKit + Tailwind for a docs-heavy + marketing site; interactive bits as Astro islands). Showcase demos are asciinema
.castrecordings (scripted-input driver for paced, re-recordable sessions — nothistory.logreplay), reused inline in docs. The in-page WASM playground is deferred (OOS: deferred) behind a stableDemoseam, with the portable-core vs native-edge boundary recorded for a future ADR + iteration plan. Portable static build (Cloudflare target via Gitea Actions, host-agnostic); no CI yet; monorepo (website/). Docs cover the full supported feature set with "planned" callouts for the unshipped minority; two wording rules bind user-facing copy — no engine name (continues ADR-0002) and no "DSL" ("simple mode" / "advanced mode"). Install docs cover prebuilt binaries + package managers (D1–D3 track the release tooling). Plan:docs/website/plans/20260604-website-implementation-plan.md